Crash in [@ base.odex]
Categories
(Fenix :: General, 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
Reporter | ||
Comment 1•2 months ago
|
||
Restart via crash ceporter led either immediately or after a short use of the browser to crash again.
Reporter | ||
Comment 2•2 months ago
|
||
These crash reports are probably also part of it. They can also be found under
Settings > About ... > Crashes
:
Reporter | ||
Comment 3•2 months ago
|
||
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.
Reporter | ||
Comment 4•2 months ago
|
||
(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.
Reporter | ||
Comment 5•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/7cc3f0a0-5bd0-41e9-a5cb-694700241218
Reporter | ||
Comment 6•2 months ago
|
||
Probably opened twice due to currently missing bug reference in the crash report: bug 1937774.
Reporter | ||
Comment 7•2 months ago
|
||
Browser was in the background at the time of the crash.
Reporter | ||
Comment 8•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/d83cdb5a-1496-40c0-9dcf-9329c0241218
Reporter | ||
Comment 9•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/c19f2278-d439-4a93-8180-3280f0241218
Reporter | ||
Comment 10•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/b3558590-324c-43b5-a2ee-cf2360241218
Reporter | ||
Comment 11•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/260ebc78-20eb-417b-9f24-ee2f70241218
Reporter | ||
Comment 12•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/1dcebaa4-a387-4f32-b9e3-898340241218
Reporter | ||
Comment 13•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/10e614a1-fe57-4909-a08f-1a8580241218
Reporter | ||
Comment 14•2 months ago
|
||
Presumably also associated:
https://crash-stats.mozilla.org/report/index/0f6d629d-1469-489e-9384-895e60241218#tab-details
Updated•2 months ago
|
Comment 15•2 months ago
|
||
The severity field is not set for this bug.
:boek, could you have a look please?
For more information, please visit BugBot documentation.
Updated•26 days ago
|
Updated•26 days ago
|
Comment 17•25 days ago
|
||
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.
Updated•25 days ago
|
Description
•