Open Bug 1494799 Opened 6 years ago Updated 11 months ago

missing crash stacks for web platform tests


(Testing :: web-platform-tests, defect)



(Not tracked)


(Reporter: karlt, Unassigned)


(Depends on 1 open bug, Blocks 2 open bugs)


No longer blocks: 1492014
Blocks: 1525801
Blocks: 1528202

Seeing that this has had no triage or other input for 5 months, James, can you comment on what is to be expected here?

Flags: needinfo?(james)

So, looking at an example, it seems like we are getting an IOError from marionette [1], which we interpret as a crash. We later call into mozcrash ([2], [3]) which is responsible for logging the stack but we aren't finding anything. So either we are misinterpreting the original IOError as a crash or we aren't getting a dump file for some reason. I wonder if the content process is crashing, but not the Chrome process? I thought we were setting MOZ_CRASHREPORTER_SHUTDOWN=1 to handle that case but right now I only see that set for fennec, so maybe that's the problem?


Flags: needinfo?(james)

No, I lie that gets set at and running the code verifies that it is indeed set. Seems like this really needs a reproducable test case to figure out what's happening.

Blocks: 1533349
Blocks: 1533656

I've seen this some more -- it seems to happen after a test, or the entire test suite, times out and we kill the process from the harness.

For mochitests this gets us stacks of all threads for the parent process, though the best would be to have them for the child process too. Especially if we're hitting a rare deadlock of some sort, getting the stacks of all threads is crucial.

Blocks: 1541556
Blocks: 1541700
Blocks: 1542315
Blocks: 1550601
See Also: → 1539449
See Also: → 1545856
Blocks: 1554557
Depends on: 1555123
Blocks: 1525503
Blocks: 1523309
Blocks: 1558373
Blocks: 1559615
Blocks: 1563052
Blocks: 1563946
Blocks: 1567692
Blocks: 1574748
Blocks: 1576981
Blocks: 1579221
Blocks: 1528067
Blocks: 1580684
Blocks: 1581445
Blocks: 1584687
Blocks: 1522334
Severity: normal → S3
Blocks: 1848092
You need to log in before you can comment on or make changes to this bug.