Closed
Bug 959153
Opened 11 years ago
Closed 11 years ago
add ability for the processor to SIGKILL the stackwalker
Categories
(Socorro :: Backend, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
76
People
(Reporter: lars, Assigned: lars)
Details
In bug 950710, we talk about a rare stackwalker failure that can bring down a processor. This bug about making the processor save itself by sending SIGKILL to a stackwalker subprocess if the processor detects misbehavior.
requirements:
- figure out how to set a timeout on subprocess io
- once the timeout exception is caught, kill the subprocess. here's help on how to do that: http://stackoverflow.com/questions/4789837/how-to-terminate-a-python-subprocess-launched-with-shell-true
- make sure that the stackwalker assassination happens at a low enough level that the worker thread can recover and continue with whatever information it has.
- see branch "hybrid-processor-killer" for a some bit rotted early work on this idea.
Assignee | ||
Comment 1•11 years ago
|
||
reopen iff the "timeout 30" solution of Bug 972857 & Bug 980435 fails to resolve the issue.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•