Closed Bug 1750352 Opened 4 years ago Closed 4 years ago

Crash in [@ EMPTY: no crashing thread identified; EmptyMinidump]

Categories

(Firefox :: General, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1749910

People

(Reporter: aryx, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This signature started to spike yesterday (2022-01-14) with 2k crashes from Linux distributions with 90% for users on 95.0.1 and 95.0.2. Based on comments, this might be related to a Firefox update (to 96) or navigation. Of course the update of a dependency is also possible. Bug 1360392 has more info about this out-of-memory signature in general.

Is anybody of you aware of changes explaining this or the issue getting tracked by distros?

Crash report: https://crash-stats.mozilla.org/report/index/d0df8d03-11ad-4ce1-a4ec-47f670220115

Flags: needinfo?(jcristau)
Flags: needinfo?(jan.steffens)
Flags: needinfo?(gsvelto)

Sorry, nothing here. This is news to me.

Flags: needinfo?(jan.steffens)
Flags: needinfo?(jcristau) → needinfo?(mh+mozilla)

This is a failure in writing the minidump, the spike caused by the HTTP3 bug in crash reports will have caused this signature to also spike. As more crash reports were generated more failed.

Flags: needinfo?(gsvelto)
Flags: needinfo?(mh+mozilla)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.