When a job i cancelled in Hudson subprocess started during the cancel run are not killed and keep running on the slave, though the log in Hudson says that the job has been aborted. The reason for this is that hudson only takes those processes into account for killing which exist at the begin of the abort action. Processes started from the job process during action are simply ignored.

This is easy to reproduce:

• from a free style job start a shell script which itself starts applications without going to background multiple times (e.g. on the Mac simply start /Applications/TextEdit.app/Contents/MacOs/TextEdit). When the job is run and cancelled the first application instance is stopped, but not the one which has been started directly after that.

This may be related to other or being the same problem reported in bugs like http://issues.jenkins-ci.org/browse/JENKINS-6188 or http://issues.jenkins-ci.org/browse/JENKINS-1805.