Closed Bug 1543481 Opened 6 years ago Closed 5 years ago

Crash in [@ libhwui.so@0x30d4e]

Categories

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

Unspecified
Android
defect

Tracking

(firefox66 wontfix, firefox67 wontfix, firefox68 wontfix)

RESOLVED WORKSFORME
Tracking Status
firefox66 --- wontfix
firefox67 --- wontfix
firefox68 --- wontfix

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-bf3bd154-8fac-444e-9410-2fccf0190406.

Seen while looking at release crash stats - this crash is only happening with Samsung phones running API 27: https://bit.ly/2Gg86ks. This is currently the #27 top crash on 66.0.2 release.

Some correlations:

98.58% in signature vs 02.68% overall) Module "libRBGLESv1_CM_adreno.so" = true
(98.58% in signature vs 02.68% overall) Module "libRBEGL_adreno.so" = true
(98.58% in signature vs 03.02% overall) android_board = msm8937
(97.36% in signature vs 02.40% overall) adapter_device_id = Adreno (TM) 308
(100.0% in signature vs 08.77% overall) Module "boot-knoxanalyticssdk.oat" = true
(98.58% in signature vs 08.71% overall) Module "knoxanalyticssdk.jar" = true
(100.0% in signature vs 11.37% overall) reason = SIGABRT
(98.58% in signature vs 09.96% overall) CPU Info = ARMv7 ARM part(0x4100d030) features: half,thumb,fastmult,vfpv2,edsp,neon,vfpv3,tls,vfpv4,idiva,idivt

Top 10 frames of crashing thread:

0 libc.so libc.so@0x1a73a 
1 libhwui.so libhwui.so@0x30d4e 
2 libhwui.so libhwui.so@0x30d4e 
3 libhwui.so libhwui.so@0x30d4e 
4 liblog.so liblog.so@0x65a3 
5 libhwui.so libhwui.so@0x9e855 
6 liblog.so liblog.so@0x65be 
7 dalvik-non moving space_619_619 (deleted) dalvik-non moving space_619_619 @0x4d151e 
8 dalvik-main space (region space)_619_619 (deleted) dalvik-main space @0xd61726d 
9 dalvik-main space (region space)_619_619 (deleted) dalvik-main space @0x3c9f4c45 

Hello, I tried to find some steps for this crash but I wasn't able to reproduce it.
I tried many scenarios to find this crash, some of the scenarios are from the comments on the signature:

  • Open multiple pages;
  • Close/reopen the app multiple times;
  • Do some searches;
  • Put the device in sleep mode and then reopen the app;
  • Browse and spend some times on netflix.com;
  • Spend some times on stream sites: Twitch, Youtube.

Build: Release 66.0.2

Devices:

  • Samsung Galaxy Note 8 (Android 9);
  • Samsung Galaxy Tab S3 (Android 8.0);
  • Samsung Galaxy Tab A (Android 7.0);
  • Samsung Galaxy J7 (Android 6.0.1).

High correlation to particular Adreno GPUs:

97.31% in signature vs 01.43% overall) adapter_driver_version = OpenGL ES 3.0 V@269.0 AU@08.01.00.312.074 (GIT@I5ed696607a) [100.0% vs 57.72% if adapter_device_id = Adreno (TM) 308]
(97.31% in signature vs 01.43% overall) adapter_driver_version_clean = OpenGL ES 3.0 V@269.0 AU@0

There are a few mentions in the comments regarding black squares:

  • My Tablet often has largeareas of black on the screen......and that happened just now, for 15 secondsorsobefore the crash.
Priority: P1 → P2

Adding 68 as affected based on the fact there are a few crashes in this signature.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 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.