Closed Bug 1409699 Opened 3 years ago Closed 3 years ago

Crash in mach_msg_trap

Categories

(Core :: General, defect)

58 Branch
Unspecified
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr52 --- fixed
firefox56 --- fixed
firefox57 --- fixed
firefox58 --- fixed

People

(Reporter: calixte, Assigned: willkg)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-ec3d373c-012c-4386-b903-5b01f0171018.
=============================================================

There are 66 crashes in nightly 58 (vs 20 in 57.0a1 and 19 in 56.0a1).
In 58, 95% of the crashes are with OS X 10.12 and 5% with OS X 10.11.

:spohl, could you investigate please ?
Flags: needinfo?(spohl.mozilla.bugs)
Virtually all of the crash comments are from me when I intentionally triggered SIGABRT crashes while working on bug 1405151. There is no reason to believe that this is a legitimate issue at this time.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(spohl.mozilla.bugs)
Resolution: --- → INVALID
there are crash reports from two dozen different installations on 57.0b9 and 58.0a1 as well.
this signature is also the top content process crash for mac users in 57.0b9 now.
Flags: needinfo?(spohl.mozilla.bugs)
Oh, interesting. I just looked at this again and it looks like the crashes that were previously landing in the "Crash in EMPTY: no crashing thread identified; OK" bucket (bug 1405151) are now showing up here with mach_msg_trap as top frame. However, there are at least a couple of different crashes here. The stacks show that there is at least one crash related to cubeb[1]. Another one has to do with shared surfaces[2].

Is there a way to split these out and be more granular based on the crashing thread stack, rather than having just one bug (this one) for all the various crashes?

[1] https://crash-stats.mozilla.com/report/index/a2e5766e-5d9c-4972-967b-13f1e0171019
[2] https://crash-stats.mozilla.com/report/index/2e177d22-8236-40dc-88f7-2e5b10171018
Status: RESOLVED → REOPENED
Flags: needinfo?(spohl.mozilla.bugs) → needinfo?(cdenizet)
Resolution: INVALID → ---
ESR52 becomes affected if we uplift bug 1405151. That would be a good thing, as we would get better crash reports from ESR52 as well.
Depends on: 1410580
This was resolved by improving the way we filter these incoming crash reports (bug 1410580).
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.