Open
Bug 1726469
Opened 4 years ago
Updated 3 years ago
Annotate OutOfMemoryError that happen while creating an event object in EventDispatcher
Categories
(GeckoView :: General, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: agi, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [geckoview:m94?] [geckoview:2023?])
A large number of our OOM exceptions are thrown while calling mozilla::widget::EventDispatcher::Dispatch, see e.g.: https://crash-stats.mozilla.org/report/index/7c420a00-4f0b-4146-967f-89a7a0210818
I think something that would be nice to explore is if we can somehow tag the crash reports with the event name that causes us to throw the exception.
|
||
Updated•4 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [geckoview:m94?]
|
||
Updated•3 years ago
|
Priority: P2 → P3
Whiteboard: [geckoview:m94?] → [geckoview:m94?] [geckoview:2023?]
|
||
Comment 1•3 years ago
|
||
When calling BoxData causes OOM, can we collect data via Telemetry or should we use MOZ_DIAGNOSTIC_ASSERT_ENABLED or MOZ_RELEASE_ASSERT etc? Of course, we should return NS_ERROR_OUT_OF_MEMORY instead of crash.
You need to log in
before you can comment on or make changes to this bug.
Description
•