Closed Bug 443730 Opened 18 years ago Closed 17 years ago

Firefox crashes when I pick Research:Fixed Income:CDs on Fidelity website

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: radrad, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 When I log in to the Fidelity website and choose to do research on CD offerings, Firefox crashes either immediately or when I try to go back to the page that displays my positions. Reproducible: Always Steps to Reproduce: 1. Find someone there who has a Fidelity account, as I am not going to tell you how to log in as me. 2. Choose "positions" on your account. 3. On the menu at the top of the Fidelity page, choose Research:Fixed Income. 4. When that page comes up, choose FDIC Insured CDs 5. Firefox generally crashes at this point. If it doesn't, go back to Portfolio Positions. Then it will crash. 6. This is new behavior in that Firefox 3.0 used to crash once in a while on the Fidelity website. Now it's almost guaranteed. IE has no problem. I also didn't have this problem with Firefox 2.3(?), the previous version. Maybe Fidelity changed something, I don't know. Actual Results: Firefox crashes and asks to send a report, restart, quit, etc. I sent a report once but am reluctant to send more due to the sensitive nature of what I am doing to cause the crash. Expected Results: Act normally. Can I download a previous version of Firefox? I hate to have to run IE to get around this problem.
Did you submit a mozilla crash report ? If you did enter about:crashes as URL and post the crash ID. If the Mozilla crash reprter didn't come up after the crash then disable the Flash plugin in tool/addons and try it again
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.