Sorting through my e-mail, I find 18 build failures since Aug 29 up until Oct 13 that looked something like this:
java.lang.IllegalThreadStateException: process hasn't exited
That ain't good, because the call to waitForProcessDeath comes immediately after a call to process.destroy()! This seems to only happen on Linux, and apparently only with Firefox.
It's not obvious what we can do about this, other than adding in a facility to support killing the process more directly using "kill -9". The trouble with that is that we don't know the PID of the process in question, and "ps" syntax can vary a great deal from Unix-to-Unix. (We have a similar facility available on Windows, though we have it disabled right now because it wasn't reliable across various versions of Windows.)