Closed Bug 320499 Opened 19 years ago Closed 17 years ago

Firefox hangs (not responding) any time i go to news.google.com

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: lenny, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 I just reformatted and re-installed my machine. I'm running WinXP SP2 on a Dual Xeon 3.0Ghz with 3gb ram and a RAID 0. For about 36 hours, the site loaded fine. Now suddenly any time I browse to the url the loader wheel in the upper right hand corner stops spinning, and firefox becomes "Not Responding" in the taskmanager. The harddrive is being accessed, and cpu load is upwards of 50%. When I click on the firefox window, another instance of firefox shows up in the task manager. I tried installing and reinstalling but no luck. Reproducible: Always Steps to Reproduce: 1. go to news.google.com Actual Results: firefox just stops responding.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051215 Firefox/1.6a1 ID:2005121521 Works for me. Can you retry in the safe mode? http://kb.mozillazine.org/Safe_Mode_(Firefox)
I have tried to replicate this problem on many different machines, but it seems that it only happens on one. When I attempt to open the page in safe mode it still crashes. I wonder if it's a dual xeon processor problem, although again, a very strange issue since it worked for the first 24 hours or so after my re-install.
You could try renaming your profile (the Mozilla folder in Application Data) and then try once again.
Summary: Firefox crashes (not responding) any time i go to news.google.com → Firefox hangs (not responding) any time i go to news.google.com
no response fro reporter 9/2006 => incomplete
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.