The patch for Bug #27061 introduced a ten second delay after a child program running in a window terminated -- this was to address a race between SIGCHLD and any output written by that program being delivered.

That behavior makes sense if the process group is expected to be empty after the child terminates.  However, some users, like myself, do things like run a bash process in a screen window and have that bash process run processes nohup in the background.  With the ten second delay, this causes each screen window to linger for ten seconds when one tries closing it -- annoying, to say the least.

I don't think that there is a fantastic way to resolve this; Linux's documentation states that a delay may legitimately exist:

PTY(7):

Data flow between master and slave is handled asynchronously, much like data flow with a physical terminal.  Data written to the slave will be available at the master promptly, but may not be available immediately. Similarly, there may be a small processing delay between a write to the master, and the effect being visible at the slave.

END MAN PAGE EXCERPT

I'm perfectly fine with some output potentially not showing up at the end (the window is dying anyway); however, a ten second delay is a problem for me.

A patch is attached to make the delay configurable.