The change for this bug is problematic for people who run background programs from their shell.  I tend to fire up programs in the background (e.g. "leafpad &") and then want to be able to close the terminal used to launch leafpad without waiting around for ten seconds.  Screen was able to do that before this patch.

When zombie resurrects quickly, remove possible legacy "destroy event".

Problem example:

1.  Enable zombie mode.
2.  Terminate the program running in a window (i.e. make the window a zombie) [1]
3.  Within 10 seconds, resurrect the window
4.  Observe:  once the 10s is up, the window (and any new processes in it!) are killed. [2]

Solution:  See enclosed patch, resurrection now removes the destroy event.

[1] if the zombie does not say 'Command detached...', then try again until it does ('Command terminated normally...' may not trigger the bug)

[2] resurrecting the destroyed window will probably cause it to be killed again, after a delay

(file #22179)

It is a race condition.

screen has two ways to shut down a window.
a) when the window filedescriptor signals eof in select().
b) when wait() returns the pid of the window process.

Whatever comes first kills the window or sends it into zombie mode.

I believe b) just should not shut down the window.
My assumption is that a) will happen shortly after b) in any case.