1021104 - crash in EMPTY: no crashing thread identified; ERROR_NO_THREAD_LIST

Status: RESOLVED DUPLICATE of bug 1021149

(Firefox :: General, defect)

Description

[juan becerra [:juanb]]

This bug was filed from the Socorro interface and is 
report bp-2498dab2-b8b0-4ee6-a714-d18212140519.
=============================================================

This signature is within the top 15 in the list of top crashers on nightly. There's no other information associated with this signature, but there are two comments and they both mention that this happened when closing Firefox.

There's no graph associated with the signature, and there doesn't seem to be a clear spike on a specific date, but the signature has been going up in the ranking in the past few days.

More reports at:

https://crash-stats.mozilla.com/report/list?product=Firefox&signature=EMPTY%3A+no+crashing+thread+identified%3B+ERROR_NO_THREAD_LIST

Comment 1

[(Away)]

Most of these crashes have this AbortMessage in the metadata:
###!!! ABORT: mismatched CxxStackFrame ctor/dtors: file c:\builds\moz2_slave\m-cen-w32-ntly-000000000000000\build\ipc\glue\MessageChannel.cpp, line 1732

That particular message showed up a couple times on the 5/21 and 5/22 builds, but picked up in volume (15+ per day) starting with the 5/24 build.

Bug 774622 also saw this on shutdown. Oddly enough, bug 924622 fixed a similar issue beginning with the 5/24 build. Without stacks it's hard to say whether they're related.

Comment 2

[(Away)]

Actually this looks just like 1021149 and has the same timing. Don't know why some of these ended up EMPTY and others valid.

Comment 3

[Lawrence Mandel [:lmandel] (use needinfo)]

Clearing tracking flags on this dup.