Closed Bug 806159 Opened 13 years ago Closed 12 years ago

Firefox becomes unresponsive within minutes after open link http://www.cringely.com/

Categories

(Firefox :: Untriaged, defect)

16 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: douglasgodfrey, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121024073032 Steps to reproduce: 1) 3 firefox windows already open 2) open a new blank firefox window 3) enter link http://www.cringely.com/ 4) scroll down using window scroll buttons 5) firefox shows severe slow-down [2-3 seconds to scroll 1 line] 6) right click on link to full article [5 seconds for context menu, 5 seconds to open link] 7) try to close the newly opened window 8) 50-100 clicks on the close button [90 seconds] were needed before the window closed 9) unresponsive script menu was never displayed 10) CPU was at 100% for 1 CPU
immediately after all windows for www.cringely.com were closed, firefox became responsive again
I can not reproduce on OS X 10.8. This may be a Snow Leopard problem. If someone could verify that would be great. Someone should try Lion as well.
What device are you using with Firefox? E.G. iMac (2011, 3.1 GHz, 6 GB of RAM)
Mac Pro 2008; 8 core 16GB RAM 16TB Disk 4TB free OS X 10.6.8 with all patches applied Adblock Plus 2.1.2 Adblock Plus Pop-Up Addpn 0.4 BetterPrivacy 1.68 NoScript 2.6
Yeah... So it is definitely on our side. It works fine on my Mac Mini (2011, dual-core, 8 GB RAM, 500GB HD) on OS X 10.8.2. However, the issue does not occur for me. Does the issue occur if you only drag the scrollbar (Do not press the arrows)?
Could either Douglas or someone on Snow Leopard please test the issue on the latest Nightly. Thanks, we can't go anywhere to I check this.
Flags: needinfo?
Looks like the relevant site has changed since this bug was reported. I am unable to reproduce the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.