Open Bug 1937868 Opened 2 months ago Updated 25 days ago

Crash in [@ base.odex]

Categories

(Fenix :: General, defect)

Firefox 135
Unspecified
Android
defect

Tracking

(firefox135 affected)

Tracking Status
firefox135 --- affected

People

(Reporter: Webworkr, Unassigned)

References

Details

(Whiteboard: [qa-triaged])

Crash report: https://crash-stats.mozilla.org/report/index/ef516c46-37be-4600-ac0e-98cfa0241217

Reason:

SIGILL / ILL_ILLOPC

Top 6 frames:

0  base.odex  base.odex@0x10d1126
1  base.odex  base.odex@0xf4f1bf
2  libart.so  libart.so@0x322dfe
3  libart.so  libart.so@0x32fe23
4  libart.so  libart.so@0x322dfe
5  libart.so  libart.so@0x32c56e

Restart via crash ceporter led either immediately or after a short use of the browser to crash again.

Other <native crash>s are logged in the aforementioned view. However, they only receive a (temporary?) crash ID without a stack trace and Socorro link and are therefore probably of no value for debugging.

(In reply to Denis Müller [:Webworkr] from comment #3)

Other <native crash>s are logged in the aforementioned view. However, they only receive a (temporary?) crash ID without a stack trace and Socorro link and are therefore probably of no value for debugging.

Further crash reports are now available.

Probably opened twice due to currently missing bug reference in the crash report: bug 1937774.

Browser was in the background at the time of the crash.

https://bugzilla.mozilla.org/show_bug.cgi?id=1937774#c1

Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [qa-triaged]

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

For more information, please visit BugBot documentation.

Flags: needinfo?(jboek)
Duplicate of this bug: 1937774
Flags: needinfo?(jboek)
Severity: -- → S4

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
Component: Crash Reporting → General
You need to log in before you can comment on or make changes to this bug.