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
{{ message }}
This repository has been archived by the owner on Jun 10, 2020. It is now read-only.
The workers are not properly killing stuck AnalysisPrograms.exe instances. Stuck instances are sapping system memory.
More needs to be done to ensure processes are killed. Not sure what.
The following is from a machine that is running one analysis worker. Only one mono instance is valid (PID 26106).
After running analyses on a machine for a while:
Might need to be turned into a loop. Some dodgy pseudo code:
while thread.alive? || system("ps -aux | grep ${pid}")
# We need to kill the process, because killing the thread leaves
# the process alive but detached, annoyingly enough.
# Sending TERM (15) instead of KILL (9) to allow clean up rather than
# dirty exit
if kill_count < max_kills - 1
Process.kill('TERM', pid)
else
Process.kill('KILL', pid)
# throw worker-level exception, email level error
fail ...
end
#killed = true # not sure what this does
# Give process time to clean up
sleep cleanup_sleep
end
The workers are not properly killing stuck AnalysisPrograms.exe instances. Stuck instances are sapping system memory.
More needs to be done to ensure processes are killed. Not sure what.
The following is from a machine that is running one analysis worker. Only one mono instance is valid (PID
26106
).After running analyses on a machine for a while:
And the output from top:
The text was updated successfully, but these errors were encountered: