Firefox 5.0 Crash after disabling addons - JSON file missing Add-ons

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
7 years ago
4 years ago

People

(Reporter: doug, Unassigned)

Tracking

({crash, stackwanted})

5 Branch
All
Windows 7
crash, stackwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Created attachment 543341 [details]
bp-3283a22b-a1bf-411a-8f72-17f912110627.txt

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build ID: 20110615151330

Steps to reproduce:

Disable all Add-ons and restarted FF 5.0


Actual results:

Application Hung / Display went transparent white (you could still see the FF 5.0 app window through the white screen.  To recover i had to "kill the process' and restart FF again.  It then came up normally with the crash report in one of the Tabs.

Processor Note:
	Priority Job; WARNING: Json file missing Add-ons; /data/socorro/stackwalk/bin/stackwalk.sh returned no header lines for reportid: 269176246; No thread was identified as the cause of the crash; No signature could be created because we do not know which thread crashed; /data/socorro/stackwalk/bin/stackwalk.sh returned no frame lines for reportid: 269176246; /data/socorro/stackwalk/bin/stackwalk.sh failed with return code 1 when processing dump 3283a22b-a1bf-411a-8f72-17f912110627


Expected results:

FireFox 5.0 (FF) should have restarted normally the first time (no crash).

Comment 1

4 years ago
Doug, have you ever seen this crash again?
Severity: normal → critical
Flags: needinfo?(doug)
Keywords: crash, stackwanted
OS: Other → Windows 7
Summary: Firefox 5.0 Crash - JSON file missing Add-ons → Firefox 5.0 Crash after disabling addons - JSON file missing Add-ons
Whiteboard: [closeme 2014-06-25]

Comment 2

4 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(doug)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-06-25]
You need to log in before you can comment on or make changes to this bug.