Closed Bug 384436 Opened 19 years ago Closed 19 years ago

Firefox nightly trunk browser closes without a peep

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: worcester12345, Unassigned)

References

()

Details

(Keywords: dataloss)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070613 Minefield/3.0a6pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070613 Minefield/3.0a6pre ID:2007061304 Go to this page: http://www.skyyindustries.com and then click on the link under the banner which says "News Release: ...." which takes you to http://www.skyyindustries.com/Newspage.html and then try to go "back". Somewhere along the line there, the entire Firefox just closes out instantly. There are no error messages, talkback, breakpad, or anything else. Just gone. I only wish Firefox would start that fast! Reproducible: Always Steps to Reproduce: 1.follow steps in the details 2. 3. Actual Results: Firefox closes all open windows without any signs or messages it was ever running. Expected Results: Should go back to previous page. No additional information at this time.
Marking dataloss, as this caused me to lose some form data I had in another window.
Flags: blocking-firefox3?
Keywords: dataloss
Summary: Browser closes without a peep → Firefox nightly trunk browser closes without a peep
I tried the pages described above with my trunk build of Firefox (2007061407). Sorry, I could not reproduce this. Everything worked just fine. (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070614 Minefield/3.0a6pre)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070613 Minefield/3.0a6pre WFM, too.
Also working for me now. I think it was a hiccup (or burp) in the java console.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Version: unspecified → Trunk
Flags: blocking-firefox3?
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.