Closed Bug 1658212 Opened 5 years ago Closed 5 years ago

Crash in [@ libxul.so (deleted)@0x55123d9] - MOZ_DIAGNOSTIC_ASSERT(!IsDead())

Categories

(Core :: DOM: Content Processes, defect)

Unspecified
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1649092
Tracking Status
firefox81 --- affected

People

(Reporter: Sylvestre, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-2bbe5d83-66f2-45dc-9b80-80ac90200807.

Top 10 frames of crashing thread:

0 libxul.so (deleted) libxul.so @0x55123d9 
1 libxul.so (deleted) libxul.so @0x55128d9 
2 libxul.so (deleted) libxul.so @0x55136c0 
3 libxul.so (deleted) libxul.so @0x551405c 
4 libxul.so (deleted) libxul.so @0x522f38c 
5 libxul.so (deleted) libxul.so @0x522ebde 
6 libxul.so (deleted) libxul.so @0x522b1aa 
7 libxul.so (deleted) libxul.so @0x522c38a 
8 libxul.so (deleted) libxul.so @0x56fc38a 
9 libxul.so (deleted) libxul.so @0x570e407 

I had that a few time but this is super rare.
Seems to be linux only

MOZ_DIAGNOSTIC_ASSERT(!IsDead()) seems to be used only in
https://searchfox.org/mozilla-central/source/dom/ipc/ContentParent.cpp

The lack of symbolication is unfortunate. The only diagnostic asserts we have for !IsDead() are in process switching code. This is probably a dupe of an existing issue.

Component: General → DOM: Content Processes

I think this is probably a dupe of bug 1649092, which is symbolicated.

I'm guessing the crash reports are not symbolicated as the most common cause is due to an update wiping out the existing binary, and a content process startup crash due to a version mismatch.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.