[Meta] Crash in [@ java.lang.OutOfMemoryError]
Categories
(GeckoView :: General, defect, P5)
Tracking
(firefox110 affected, firefox111 affected, firefox112 affected)
People
(Reporter: fluffyemily, Unassigned)
References
(Depends on 6 open bugs)
Details
(Keywords: crash, meta)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/e80a9f00-3fbd-41d4-8f52-652780210729
Java stack trace:
java.lang.OutOfMemoryError
Reporter | ||
Comment 1•3 years ago
|
||
Agi to create some subtasks that we can schedule in
Comment 2•3 years ago
|
||
I have been looking at the reports, it looks like a good number of them (about half from what I can see) are while creating an EventDispatcher event, it would be really nice if we could annotate the crash report for those somehow (e.g. with the size of the message and/or the message type).
A suspiciously large number of the crashes is in mozilla::java::GeckoSurfaceTexture::DestroyUnused
.
And the third group is from GeckoTelemetryDelegate::DispatchHistogram
.
There's a problem with socorro that's preventing me from searching this crashes to get accurate numbers, so I'm gonna wait for that before opening dependents so that I can look at the trends and see if any of these got worse recently.
Updated•2 years ago
|
Updated•1 year ago
|
Comment 3•6 months ago
•
|
||
We're seeing a big spike in Java OOM crashes since Fx125 shipped (~10x higher volume than previous releases). Can we please investigate what might have changed to have caused it?
EDIT: Actually, looking at crash-stats, it looks like this might have started spiking in 124.2.0.
Updated•11 days ago
|
Description
•