Closed
Bug 1663854
Opened 5 years ago
Closed 5 years ago
Crash in nsZipHandle::Init [@ PR_MD_LSEEK64 | FileAvailable64 ]
Categories
(Core :: Networking: JAR, defect)
Core
Networking: JAR
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jstutte, Unassigned)
Details
Crash Data
The three crashes I see now point to nsZipHandle::Init. This could happen, if OpenNSPRFileDesc returned NS_OK but did not create a valid FD for some reason. There seems to be the theoretical possibility that ConvertWinError returns NS_OK, though it sounds unlikely that GetLastError did return 0. But a ConvertWinErrorfunction that may return NS_OK seems odd.
These are start-up crashes on the main thread opening omni.ja, it seems.
| Reporter | ||
Updated•5 years ago
|
Crash Signature: [@ PR_MD_LSEEK64 | FileAvailable64 ]
Comment 2•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Flags: needinfo?(valentin.gosu)
You need to log in
before you can comment on or make changes to this bug.
Description
•