Closed
Bug 973845
Opened 10 years ago
Closed 10 years ago
Latest nightly crashing on or shortly after starting
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 973207
People
(Reporter: olly, Unassigned)
Details
(Whiteboard: [bugday-20140224] )
Crash Data
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1838.2 Safari/537.36 Steps to reproduce: 1. Update to latest nightly (30.0a1 2014-02-17) on Windows 2008 Server R2 x64. 2. Launch nightly. 3. Attempt to navigate anywhere (if you get a chance). Actual results: It will crash (bomb out and return to crash reporter) on or very soon after starting up. Upon reopening, I went to about crashes and started to load https://crash-stats.mozilla.com/report/index/db5b5e88-d5a7-467d-b1b8-b64e82140218 before crashing again. A minute or so earlier it was https://crash-stats.mozilla.com/report/index/ccbd83a3-31e7-4f65-98f1-8a39a2140218. It crashes when launched in Safe mode. Resetting Firefox doesn't help either. I'm seeing the crash both on my base machine, and in Virtualbox VMs (again, Windows 2008 Server R2 x64). Expected results: Nightly should work normally :-)
Comment 1•10 years ago
|
||
According to the Bug mentioned in the crash report, it happened because of Memory dump. Try these step to solve the crash *http://kb.mozillazine.org/Memory_Leak
Updated•10 years ago
|
Whiteboard: [bugday-20140224]
Comment 2•10 years ago
|
||
Please check if the issue occurs using Firefox in safe mode (with your addons disabled): http://support.mozilla.com/kb/Safe+Mode Or on a new, empty profile: http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager
Comment 3•10 years ago
|
||
olly, thanks for the report! I think this is a duplicate for bug 973207 and has been fixed in the latest Nightly.
Status: UNCONFIRMED → RESOLVED
Crash Signature: [@ mozilla::net::nsHttpConnection::Close(tag_nsresult) ]
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•