Closed Bug 471879 Opened 16 years ago Closed 16 years ago

Couldn't relaunch with crash reporter open {EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE}

Categories

(Firefox :: Session Restore, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 457316

People

(Reporter: zandr, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5

I just had an odd problem where I ended up with two instances of crash reporter open. I think it came from clicking links in Tbird that were trying to open tabs while FF had crashed and the crash reporter was open.

From that point, clicking the "Restart Firefox" button, clicking either restore session or start new session, would crash immediately. Only when I got rid of both instances of CR could I get FF to launch.

Look for crash reports with a timestamp of a few minutes ago. Most of them had no comments, one I typed in "Can't Launch", source IP is 75.37.37.16

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1.
2.
3.
Can you give the crash ids. We get dozens a day, so we can't find "Your's".
I have no idea where they are.

Perhaps that should be its own bug. "Crash IDs are not obvious to user"
You can't reproduce at all? Even is Safe Mode?
Summary: Couldn't relaunch with crash reporter open → Couldn't relaunch with crash reporter open {EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE}
Since I don't know what I was doing to get it to crash in the first place, no, I can't reproduce the crash reporter relaunch issue.

And, what do you mean by safe mode in this context?
most of your crashes are bug 457316

one is bug 470864
two are bug 471968
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.