Closed
Bug 1363306
Opened 8 years ago
Closed 8 years ago
Crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::dom::ContentChild::FatalErrorIfNotUsingGPUProcess | libxul.so@0xe1c665 | mozilla::dom::TabChild::InitRenderingState
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | affected |
People
(Reporter: calixte, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, regression, Whiteboard: [clouseau])
Crash Data
This bug was filed from the Socorro interface and is
report bp-2a72cb92-d246-4e1c-82d1-ef07a0170508.
=============================================================
There 3 crashes from the same installation in nightly 55 with buildid 20170508100218. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1350634.
[1] https://hg.mozilla.org/mozilla-central/rev?node=8d5920dc4472dd624e30017d3b1f15e1167e588f
Flags: needinfo?(dvander)
It looks like this crash has died down. Almost certainly this is the bug where our updater replaces the content process while the parent is still running, and so any sort of IPC mismatch fails. There isn't much we can do about that except hope the updater bug gets fixed.
In bug 1333056 I'm trying to at least categorize these crashes into one bucket.
Flags: needinfo?(dvander)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•