Closed
Bug 1476077
Opened 6 years ago
Closed 5 years ago
Crash in libhwui.so@0x86d4e
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox61 wontfix, firefox62 wontfix, firefox63 wontfix, firefox64 fix-optional, firefox65 fix-optional)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox61 | --- | wontfix |
firefox62 | --- | wontfix |
firefox63 | --- | wontfix |
firefox64 | --- | fix-optional |
firefox65 | --- | fix-optional |
People
(Reporter: marcia, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
This bug was filed from the Socorro interface and is report bp-2649ac19-b19d-499a-b81d-448d80180716. ============================================================= Seen while looking at crash stats - regression affecting Samsung devices running API 26: https://bit.ly/2LnY29f. Top crashing device is Samsung Galaxy S7. Currently this is the #19 top browser crash on 61 release. One comment "dragging finger up" Top 10 frames of crashing thread: 0 libc.so libc.so@0x4b748 1 libhwui.so libhwui.so@0x86d4e 2 libhwui.so libhwui.so@0x86d4e 3 liblog.so liblog.so@0x6685 4 libhwui.so libhwui.so@0x3a57e 5 liblog.so liblog.so@0x66a2 6 boot-apache-xml.oat boot-apache-xml.oat@0xb463 7 dalvik-main space (region space)_3314_3314 (deleted) dalvik-main space @0xdae6f67 8 boot-framework.oat boot-framework.oat@0xc5de6d 9 dalvik-main space (region space)_3314_3314 (deleted) dalvik-main space @0x1d606561 =============================================================
Reporter | ||
Comment 1•6 years ago
|
||
62 is affected, but so far in beta the volume is low.
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Low volume crash on release; too late for a fix in 63.
Reporter | ||
Comment 3•5 years ago
|
||
Closing this one out as there are no crashes on 68.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•