Closed
Bug 264177
Opened 20 years ago
Closed 19 years ago
firefox "unexpectedly quits" (dialog box comes up & talkback opens) whenever I open it
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mfjakron87, Assigned: bugzilla)
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/85.8.2 (KHTML, like Gecko) Safari/85.8 Build Identifier: Problem also occurs in Mozilla, Camino, Netscape - in short, all Mozilla & Netscape browsers. Reproducible: Always Steps to Reproduce: 1. Open Firefox. 2. Wait. 3. Cross fingers. Actual Results: Firefox quits. Info box comes up saying that Firefox has unexpectedly quit. Talkback opens and asks you to send a bug report to Netscape. Expected Results: It should have opened.
Comment 1•20 years ago
|
||
Justin, could you post the Talkback ID of the crash to this bug report?
| Reporter | ||
Comment 2•20 years ago
|
||
Talkback ID: TB1319237H
Comment 3•20 years ago
|
||
WFM: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050527 Firefox/1.0+ Justin, could you go to mozilla.org, click on the developers tab, download a nightly build at the bottom of the page, and try retesting this bug with that?
| Reporter | ||
Comment 4•20 years ago
|
||
(In reply to comment #3) Done. It appears to work now.
Comment 5•19 years ago
|
||
I also have this problem. I have a very stable 10.4.2 system with the latest Firefox. I run Safari and Firefox side by side but use FF as my default broweser. There are quite a few sites that make FF unexpectedly quit and without exception, each of those troublesome site work perfectly well in Safari. Thats not a scientific report but it does indicate that there is something amiss. Thats all I can tell you.
Comment 6•19 years ago
|
||
Marking WFM for the reporter from comment 4 - trunk build working fine, branch build had the problem. Comment 5 is a different issue to the origional report.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•