Closed
Bug 1369057
Opened 8 years ago
Closed 7 years ago
firefox.exe, version: 55.0.0.6360, Exception code: 0xc0000005 on startup
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bobfishr, Unassigned)
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Steps to reproduce:
Updated nightly from previous day to 55.0.0.6360 using automatic update.
Windows 10 home 64 bit ver1607 build 14393.1198 16gb intel core i7 nvidia Geforce GT730
Actual results:
Application will not launch after nightly update to 55.0.0.6360. Windows event 1000 with Exception code: 0xc0000005
Reporter | ||
Comment 1•8 years ago
|
||
The initial update process caused windows to crash.
Updated•8 years ago
|
Component: Untriaged → Startup and Profile System
Product: Firefox → Toolkit
Comment 2•8 years ago
|
||
Bob, I'm assuming that the Firefox crash reporter doesn't show up for this crash. I don't know how technical you are, but it would be really valuable to have a dump file for the crashing process. Are you perhaps capable of debugging or collecting a minidump? https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/ has some possible instructions, although they require some technical chops.
Flags: needinfo?(bobfishr)
Reporter | ||
Comment 3•8 years ago
|
||
Flags: needinfo?(bobfishr)
Reporter | ||
Comment 4•8 years ago
|
||
Here is the mini dump you requested.
Reporter | ||
Comment 5•8 years ago
|
||
I have the windows memory dump file as well. Ill have to upload that elsewhere if it would be helpful.
Comment 6•8 years ago
|
||
The minidump is interesting by itself:
> firefox.exe!mozilla::GetBootstrap(const char * aXPCOMFile) Line 412 C++
firefox.exe!NS_internal_main(int argc, char * * argv, char * * envp) Line 298 C++
firefox.exe!wmain(int argc, wchar_t * * argv) Line 118 C++
We're crashing with a null sTop at https://dxr.mozilla.org/mozilla-central/rev/7b8937970f9ca85db88cb2496f2112175fd847c8/xpcom/glue/standalone/nsXPCOMGlue.cpp#412
glandium, can you think of a reason why XPCOMGlueLoad would have succeeded but sTop is still null?
The modules list in the minidump is entirely Firefox and windows DLLs, nothing else strange.
Flags: needinfo?(mh+mozilla)
Comment 7•8 years ago
|
||
I can see one corner case from the code in XPCOMGlueLoad that could lead to that: an empty dependentlibs.list.
Bob, can you check in your Firefox install directory whether the dependentlibs.list file is empty?
Flags: needinfo?(mh+mozilla) → needinfo?(bobfishr)
Reporter | ||
Comment 8•8 years ago
|
||
Flags: needinfo?(bobfishr)
Reporter | ||
Comment 9•8 years ago
|
||
Yes, Dependentlibs.list is empty.
Updated•8 years ago
|
Attachment #8873267 -
Attachment mime type: application/octet-stream → text/plain
Comment 10•8 years ago
|
||
The file you attached is not empty, but it's also not valid. So there are two problem here:
- The init code doesn't like your dependentlibs.list file and doesn't gracefully fail.
- Your dependentlibs.list file is corrupt in the first place.
I guess the latter is related to comment 1?
The best we can do here is fail in a more graceful way, but that won't solve your problem, which is that your Firefox install is corrupted.
Reporter | ||
Comment 11•8 years ago
|
||
OK, Third try to update this post. Is there anything more I can provide? I'm assuming I should un-install, re-install Nightly to correct the problem. Is there some other recovery method you want me to try?
Thanks,
Bob
Here is the Bugzilla error I received twice before today:
DBD::mysql::db do failed: Lock wait timeout exceeded; try restarting transaction [for Statement "UPDATE bugs SET delta_ts = ? WHERE bug_id = ?"]
Comment 12•7 years ago
|
||
Yes, a reinstall *should* fix this. It might be interesting why this happened, but since the update logs probably don't have this any more, unless you can reproduce the problem I'm going to close this. I'm sorry you had this problem.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•