search

necrolyte2 / beast-mcmc

Automatically exported from code.google.com/p/beast-mcmc
0 stars 0 forks source link

BEAST v1.8.1 is not terminating leaving 'zombie' processes #754

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
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.

Original issue reported on code.google.com by ramb...@gmail.com on 17 Dec 2014 at 10:19

GoogleCodeExporter commented 9 years ago

Original comment by ramb...@gmail.com on 3 Feb 2015 at 2:36