Fenix 106.1.0 Crash Report [@ @0xe5e5e5e5e5e5e5e5 ]
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
People
(Reporter: geeknik, Unassigned)
References
()
Details
(Keywords: reporter-external, Whiteboard: [reporter-external] [client-bounty-form] [verif?])
Crash Data
After reading an update to crash statistics, I went searching for the UAF signature and found https://crash-stats.mozilla.org/report/index/8db26d80-9ac0-4685-af87-872440221031, dated 31 October 2022. This seems like one of those bugs that needs some attention as it appears to have affected Fenix for some time.
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
These crashes don't look very actionable. Maybe gsvelto has some ideas.
Comment 2•2 years ago
|
||
The first Mozilla controlled code in this crash is in JS.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
We are jumping into a UAF pointer which is indeed unfortunate... but the stacks in the few crashes here are different and often completely jumbled up. They don't look to be coming from a single issue and some might be caused by bad hardware. I don't think this is actionable. Also generally speaking you won't see the poison pattern in the crash signature - this one in particular was already visible before we fixed bug 1493342 - but in the crash address.
Comment 4•2 years ago
|
||
There's no real information to go on here, so I'm going to unhide this.
Updated•2 years ago
|
Updated•8 months ago
|
Description
•