Closed Bug 536391 Opened 14 years ago Closed 13 years ago
When scrolling down, the whole PC freezes and must be rebooted
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:126.96.36.199) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:188.8.131.52) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729) I use Samsung NC20. Since upgrading to 3.5, I experience freezing of the whole PC when I attempt to use the scroll-bar in some websites. The STATCOUNTER site above is only an example, but with this site the freeze is repeatable. Reproducible: Always Steps to Reproduce: 1. www.statcounter.com 2. Login to my project 3. Go to Recent Visitor Activity. 4. Scroll down using the mouse-pad and right-hand scroll bar. Actual Results: Whole PC Freezes. Cannot reclaim and must switch-off. I have waited 5 minutes to see if system recovers. It doesn't. Expected Results: Screen should scroll-down Happens with a number of sites, but Statcounter is the one that I can easily reproduce.
Can you try basic troubleshooting and see if that works? For instance: - Firefox's safe-mode to exclude extension/theme problems - a new profile - a clean reinstallation http://support.mozilla.com/en-US/kb/Safe+Mode http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
Have not experienced any such problem for some months and specifically tested the site with which I experienced problems. Thanks for reminder - I had, of course, forgotten! Thanks for the fix.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.