On 29/02/16 12:03 PM, Benjamin Smedberg wrote:
On 2/27/2016 9:06 PM, Randell Jesup wrote:
months until recently it popped up a bit). Note that this failure
*never* results in a crashdump, and I've never seen it locally, just in
Automation.
What we do know:
* Exit code -11 is evidence a SIGSEGV (crash).
This I don't know, but somebody may know (+ted):
* Are we sure that the crash is happening in firefox.exe? Or is it
possible that some other process is crashing and taking down our
test harness with it?
* Can somebody point to exactly what line of code in the test harness
collects the -11 code?
Returning -signal is an idiom from python's subprocess stdlib that
mozprocess replicates:
https://dxr.mozilla.org/mozilla-central/source/testing/mozbase/mozprocess/mozprocess/processhandler.py#593
* Is there no crash dump because the crash reporter is turned off?
o If it's turned on, is the crash reporter itself crashing? Or is
the test harness not picking up the crash dump?
I've seen shutdown crashes that don't generate dumps before. Like bug
1228595. Ted theorized that the chrome process is too far into shutdown
to handle the crash properly.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
