Start-up crash [@ nsZipArchive::OpenArchive ]
Categories
(Core :: Networking: JAR, defect)
Tracking
()
People
(Reporter: scoobidiver, Unassigned)
References
Details
(Keywords: crash, csectype-wildptr, sec-moderate, Whiteboard: [necko-backlog])
Crash Data
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
| Assignee | ||
Updated•15 years ago
|
| Reporter | ||
Comment 3•14 years ago
|
||
Updated•10 years ago
|
Comment 4•10 years ago
|
||
Updated•10 years ago
|
Comment 5•10 years ago
|
||
Comment 6•9 years ago
|
||
Comment 7•9 years ago
|
||
Updated•3 years ago
|
Comment 9•3 years ago
|
||
clear wildptr crashes, ongoing at a low rate. spike oct 6 seems to be a single client reporting N times
removing automatic/old priority
Updated•3 years ago
|
Updated•3 years ago
|
Comment 10•3 years ago
|
||
This is not a useful bug right now. In the past 3 months, looking at only "recent" Firefox versions (110 and higher) there were a total of 42 crashes from 7 distinct individuals. 14 of those were two Fenix users, and 28 were Desktop. 3 of the desktop users crashed once each (two null derefs and a EXCEPTION_ILLEGAL_INSTRUCTION), another had 11 EXCEPTION_PRIV_INSTRUCTION crashes, and the last had 14 crashes spread over 6 weeks that were a mix of read and write violations. I don't see any that looked like UAF
All 42 were start-up crashes, not influenced by any potentially malicious web code. The bad instruction crashes should definitely be corruption (of memory, or the firefox executable). Maybe the others are memory problems, too, since only a few individuals are crashing but all Firefox users should be opening the same omni.jar files using the same start-up code.
Comment 11•3 years ago
|
||
Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit BugBot documentation.
Description
•