Issue 754 in beast-mcmc: BEAST v1.8.1 is not terminating leaving 'zombie' processes

[beast...@googlecode.com]

Status: Accepted
Owner: ramb...@gmail.com
Labels: Type-Defect Priority-Critical beast v1.8.1 Milestone-Release1.8.2

New issue 754 by ramb...@gmail.com: BEAST v1.8.1 is not terminating
leaving 'zombie' processes
https://code.google.com/p/beast-mcmc/issues/detail?id=754

Java VM only terminates when all user threads have finished. Exiting the
main() function normally at the end of the BEAST run should terminate the
process but it doesn't, suggesting that another user thread is still
active. When a GUI is present, this is desired behaviour because it is up
to the user to select 'quit' from the menu.

Previously main() finished with:

if (!window) {
System.exit(0);
}

Which is a solution. This was removed in v1.8.1 because the assumption was
it wasn't needed. The better solution would be to find the thread that is
still running and correctly terminate it. If this is not possible, then
revert this hack solution.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[beast...@googlecode.com]

Updates:
Status: Fixed

Comment #1 on issue 754 by ramb...@gmail.com: BEAST v1.8.1 is not

terminating leaving 'zombie' processes
https://code.google.com/p/beast-mcmc/issues/detail?id=754

(No comment was entered for this change.)