1897806 - Crash in [@ libart.so | dalvik-alloc space (deleted)]

Status: NEW

(Firefox for Android :: General, defect, P5)

Description

[twhite]

Crash report: https://crash-stats.mozilla.org/report/index/f8bcb685-c845-4b77-97c5-0f6a10240519

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames:

0  libart.so  libart.so@0x119f48
1  libart.so  libart.so@0xe6532
2  dalvik-alloc space (deleted)  dalvik-alloc space (deleted)@0x1bceef
3  dalvik-main space (deleted)  dalvik-main space (deleted)@0x7a173f
4  dalvik-alloc space (deleted)  dalvik-alloc space (deleted)@0x1ba02f
5  libart.so  libart.so@0xe6532
6  system@[e-mail]  system@[e-mail]@0x1f41c7
7  dalvik-main space (deleted)  dalvik-main space (deleted)@0x79363f
8  system@[e-mail]  system@[e-mail]@0xb042e7
9  dalvik-main space (deleted)  dalvik-main space (deleted)@0x79363f

https://crash-stats.mozilla.org/search/?release_channel=release&signature=%3Dlibart.so%20%7C%20dalvik-alloc%20space%20%28deleted%29&product=Fenix&date=%3E%3D2024-05-19T00%3A00%3A00.000Z&date=%3C2024-05-20T00%3A00%3A00.000Z&_facets=install_time&_facets=version&_facets=address&_facets=moz_crash_reason&_facets=reason&_facets=build_id&_facets=platform_pretty_version&_facets=signature&_facets=useragent_locale&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

Comment 1

[Andrew McCreight [:mccr8]]

This looks Android-specific and not easily attributable to any specific part of Gecko, so I'll move this to Fenix. Maybe better symbols would help?

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

For more information, please visit BugBot documentation.

Comment 3

[Chris Peterson [:cpeterson]]

More than 98% these crash reports are from x86 devices running Android 5.0 or 5.1.

These bugs are probably unactionable OOMs, but why was there was a big spike in crash volume on 2024-05-10? Some external event?

Comment 4

[Andrew McCreight [:mccr8]]

(In reply to Chris Peterson [:cpeterson] from comment #3)

These bugs are probably unactionable OOMs, but why was there was a big spike in crash volume on 2024-05-10? Some external event?

That could be when we started removing addresses from crash signatures.

Comment 5

[Gabriele Svelto [:gsvelto]]

Yes, the spike was caused by bug 1895527 changing these signatures, it's not a regression, the volume was probably the same, but spread over dozens of different signatures.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

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

• Top 10 AArch64 and ARM crashes on beta

For more information, please visit BugBot documentation.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit BugBot documentation.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

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.

Comment 9

[Gabriele Svelto [:gsvelto]]

Not a crash reporting bug, we still have to figure this one out.