Closed
Bug 1784884
Opened 4 years ago
Closed 3 years ago
Crash in [@ libutils.so@0x10918] on Android 11
Categories
(GeckoView :: General, defect, P5)
Tracking
(firefox103 wontfix, firefox104 wontfix, firefox105 affected)
RESOLVED
WORKSFORME
People
(Reporter: amejia, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/0caebd41-840e-4f2f-9531-d2c600220815
Reason: SIGSEGV / SEGV_MAPERR
Top 4 frames of crashing thread:
0 libutils.so libutils.so@0x0000000000010918
1 libandroid_runtime.so libandroid_runtime.so@0x00000000000f71c8
2 boot-framework.oat boot-framework.oat@0x00000000001f8930
3 None @0x00000071d7a80b00
Updated•4 years ago
|
status-firefox103:
--- → affected
status-firefox104:
--- → affected
status-firefox105:
--- → affected
Priority: -- → P5
Summary: Crash in [@ libutils.so@0x10918] → Crash in [@ libutils.so@0x10918] on Android 11
Comment 1•4 years ago
|
||
This crash only affects Android 11, so it might be a recent Google regression in Android 11. It doesn't look actionable for us.
Updated•4 years ago
|
Comment 2•3 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Severity: S2 → S3
Comment 3•3 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Component: Core → General
You need to log in
before you can comment on or make changes to this bug.
Description
•