Closed Bug 234863 Opened 22 years ago Closed 22 years ago

When I open Tools > Options, FireFox crashes.

Categories

(Firefox :: Settings UI, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: erwin, Assigned: bugzilla)

References

Details

User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040218 Firefox/0.8 When I open Tools > Options, FireFox crashes. I dont know what is wrong, I just know it doesnt like me using the option panel ;-) Reproducible: Always Steps to Reproduce: 1.Goto the Tools menu 2.Choose Options Actual Results: FireFox Crashes Expected Results: Open the Options panel
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040224 Firefox/0.8 Confirmed. However, I do get one stage further. The last option tab that I'd opened when it worked, was "Extensions" and I do still get the options panel opening with this tab selected. I can select any tab apart from "General" with no problem. As soon as I select the "General" tab, Firefox crashes.
Works for me using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040224 Firefox/0.8.0+ Please try installing into a new directory and creating a new profile, using the MozillaFirebird.exe -p switch, and report your results here
I get the same thing using win 98SE and my last night install. I was going in to try turning off tab related extensions because I was unable to close individual tabs ( click box, cntrl/w, right click contex menu all fail. I don't know if it will help, but here are the register dumps from 2 tries: FIREFOX caused an invalid page fault in module FIREFOX.EXE at 0197:0087affd. Registers: EAX=00000000 CS=0197 EIP=0087affd EFLGS=00010206 EBX=00dc620a SS=019f ESP=00ced404 EBP=00ced44c ECX=023676f0 DS=019f ESI=00ced4d4 FS=28b7 EDX=009c87b8 ES=019f EDI=00ced670 GS=0000 Bytes at CS:EIP: ff 60 0c 83 6c 24 04 04 e9 d9 ee ff ff 83 6c 24 Stack dump: 0087a7e6 00ced4d4 00ced458 00ced4d4 00e1e470 7800b317 00000000 02367690 00dc5f0a 00000000 00000000 02367698 00e00084 02367698 00e143c8 00cee318 FIREFOX caused an invalid page fault in module FIREFOX.EXE at 0197:0087affd. Registers: EAX=00000000 CS=0197 EIP=0087affd EFLGS=00010202 EBX=00dc620a SS=019f ESP=00ced3c0 EBP=00ced408 ECX=02104600 DS=019f ESI=00ced490 FS=5cff EDX=009c87b8 ES=019f EDI=00ced62c GS=0000 Bytes at CS:EIP: ff 60 0c 83 6c 24 04 04 e9 d9 ee ff ff 83 6c 24 Stack dump: 0087a7e6 00ced490 00ced414 00ced490 00e1e470 7800b317 00000000 02105cd0 00dc5f0a 00000000 00000000 02105cd8 00e0005c 02105cd8 00e143c8 00cee318
*** Bug 235470 has been marked as a duplicate of this bug. ***
Out of those people seeing it, how many have the Tabbed Browser Extension installed? I would like someone seeing this issue to at least try with a new profile and all extensions disabled, that should be easy enough to try. Register dumps aren't much help, I'm really really looking forward to getting talkback in nightlies again.
(In reply to comment #5) I was not using TBE. However, I had originally extracted the first 20040224 zip over the top of the install version. I have now extracted the newer 200420224 zip into a new directory and it works (using the old profile).
Sorry, forgot to say that I'm now extremely happy with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040224 Firefox/0.8.0+
oh, that'll do it for sure, that's fallout from splitting how prefs inherit from the GRE. We always recommend installing new builds into a clean directory for that reason (the installer in 0.9 will actually do proper removal of potentially conflicting files). I have nightly install scripts that nuke the existing files before extracting for that very reason. Anyone else?
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040307 Firefox/0.8.0+
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.