Open Bug 1903803 Opened 1 year ago Updated 3 hours ago

startup Crash in [@ libskia.so] with Android 21-27 devices

Categories

(Firefox for Android :: Crash Reporting, defect)

Firefox 127
Unspecified
Android
defect

Tracking

()

Tracking Status
firefox127 --- affected
firefox128 --- affected
firefox129 --- affected
firefox130 --- affected
firefox139 --- affected

People

(Reporter: aryx, Unassigned)

Details

(Keywords: crash)

Crash Data

660 crashes from 539 devices for Firefox 127.0, crashes got more frequent compared to the 126 branch.

Only Android 21-27 are affected, or newer versions create different stacks.

Crash report: https://crash-stats.mozilla.org/report/index/9e64e0a4-8dee-4d5d-8cb1-abce00240620

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames:

0  libskia.so  libskia.so@0x44702c
1  libskia.so  libskia.so@0x3de59c
2  libandroid_runtime.so  libandroid_runtime.so@0x111880
3  boot-framework.oat  boot-framework.oat@0x1e677ec
4  ?  @0x0000007d7d31fe80
5  ?  @0x0000007d7d4cdbf0
6  ?  @0x0000007d7d4c6bcc
7  ?  @0x0000007d7d796f18
8  ?  @0x0000007d7d309914
9  ?  @0x0000007d7d4a0dfc

Gabriele, is it possible to figure out where symbols for these libraries might live?

Flags: needinfo?(gsvelto)
Flags: needinfo?(jnicol)

Crashing threads are BrowserIcons-th, DefaultDispatch, and ThumbnailStorag, so this seems like a Fenix regression rather than a platform graphics one.

Component: Graphics → General
Flags: needinfo?(jnicol)
Product: Core → Fenix
Version: unspecified → Firefox 127

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on release

For more information, please visit BugBot documentation.

Keywords: topcrash

(In reply to Ryan VanderMeulen [:RyanVM][PTO June 24-28] from comment #1)

Gabriele, is it possible to figure out where symbols for these libraries might live?

Possibly in Android system builds, but we haven't managed to scrape those yet, and I'm not even sure if the symbols are really available or the binaries are fully stripped.

Flags: needinfo?(gsvelto)

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on release (startup)

For more information, please visit BugBot documentation.

The severity field is not set for this bug.
:amejia, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(amejiamarmol)

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

Flags: needinfo?(amejiamarmol)
Severity: -- → S2

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

Keywords: topcrash

The Bugbug bot thinks this bug should belong to the 'Fenix::Crash Reporting' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Crash Reporting

Reproduced today on Beta 139.0b10 on a Huawei MediaPad M3 Lite (Android 7): https://crash-stats.mozilla.org/report/index/9c9123a5-91c8-450b-b40b-7c9b60250519#tab-bugzilla

You need to log in before you can comment on or make changes to this bug.