Closed Bug 1493635 Opened 3 years ago Closed 2 years ago

Crash in libhwui.so@0x86de6

Categories

(Firefox for Android Graveyard :: General, defect, P3)

Unspecified
Android
defect

Tracking

(firefox64 wontfix, firefox65 fix-optional, firefox66 ?)

RESOLVED WORKSFORME
Tracking Status
firefox64 --- wontfix
firefox65 --- fix-optional
firefox66 --- ?

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is
report bp-297b4aed-6c21-484d-9ae3-ee7020180812.
=============================================================

Top 10 frames of crashing thread:

0 libc.so libc.so@0x4bd10 
1 libhwui.so libhwui.so@0x86de6 
2 libhwui.so libhwui.so@0x86de6 
3 liblog.so liblog.so@0x66db 
4 libhwui.so libhwui.so@0x389e2 
5 liblog.so liblog.so@0x66f6 
6 boot-framework.oat boot-framework.oat@0xd97270 
7 dalvik-main space (region space)_1650_1650 (deleted) dalvik-main space @0x1cb36267 
8 dalvik-non moving space_1650_1650 (deleted) dalvik-non moving space_1650_1650 @0xec0562 
9 system@framework@boot-ext.art system@framework@boot-ext.art@0x28f62 

=============================================================

This looks like a Qualcomm-specific bug:


(100.0% in signature vs 02.23% overall) android_board = sdm845
(100.0% in signature vs 02.25% overall) CPU Info = ARMv1 Qualcomm part(0x51008030) features: half,thumb,fastmult,vfpv2,edsp,neon,vfpv3,tls,vfpv4,idiva,idivt
(100.0% in signature vs 02.25% overall) adapter_device_id = Adreno (TM) 630

Filing it so we can keep track of it.
Very low volume crash even on release. I'm marking this fix-optional for 65 but we are happy to take a patch in nightly if anyone investigates.
Priority: -- → P3
Since this is a hardware-specific bug at this volume we might just close it. The offending driver/library has probably been fixed upstream.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.