You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After my last run of cadiaplayer, I had a leftover process that was consuming most of the memory on the box, causing significant swapping. I didn't see which it was, so it pretty much invalidated the collected statistics.
EDIT: From further research and testing, it seems like the issue is not the reliability of killing processes, but just the ability to kill process subtrees instead of an individual process. That will be available in Java 9, which sounds like a good long-term solution.
The text was updated successfully, but these errors were encountered:
AlexLandau
changed the title
More aggressive options for killing bad processes
Kill process subtrees, not individual processes
Mar 21, 2016
AlexLandau
changed the title
Kill process subtrees, not individual processes
Kill process subtrees, not individual processes, after timeouts
Mar 21, 2016
After my last run of cadiaplayer, I had a leftover process that was consuming most of the memory on the box, causing significant swapping. I didn't see which it was, so it pretty much invalidated the collected statistics.
This suggests that kill -kill -1234 (for script PID 1234) might work for POSIX-reliant scripts like cadiaplayer's, if we can somehow figure out the script PID from Java: http://askubuntu.com/questions/520107/how-to-kill-a-script-running-in-terminal-without-closing-terminal-ctrl-c-doe
EDIT: From further research and testing, it seems like the issue is not the reliability of killing processes, but just the ability to kill process subtrees instead of an individual process. That will be available in Java 9, which sounds like a good long-term solution.
The text was updated successfully, but these errors were encountered: