Recently FireFox often has been causing 100% CPU usage and locks up until it finishes the process (various ones). Clearing cookies/cache didn't help. Any ideas?
Windows 2000 SP4, 1g RAM, Firefox 9.0.1 We keep IE6 and Firefox open simultaneously for 2 different mail accounts. Firefox was always much faster even with 3 or 4 tabs open, but for the past couple of weeks when trying to update a screen the CPU suddenly goes to 100% usage and of course nothing will move until the particular process is finished. Closing one or more tabs does not help. If I close Firefox completely with Task Manager CPU usage goes back down to nil. After restarting Firefox CPU usage may or may not go back up depending upon whether it tries to continue the previous task that was locking it up. It did not do this with Firefox 3.6 but then again it didn't happen immediately after updating to 9.0.1 either.
Additional System Details
A few times a week
This started when...
The problem occurred for the first time after printing USPS postage through eBay. (Same process, same thing next day.)
- Shockwave Flash 11.1 r102
- NPRuntime Script Plug-in Library for Java(TM) Deploy
- Next Generation Java Plug-in 1.6.0_30 for Mozilla browsers
- Adobe PDF Plug-In For Firefox and Netscape 8.3.1
- Client Keeper KeyPro Keyboard Protector for Multi Browser
- npxwebplugin_file v.184.108.40.206
- npxwebplugin v.220.127.116.11
- Npdsplay dll
- DRM Netscape Network Object
- DRM Store Netscape Plugin
- User Agent: Mozilla/5.0 (Windows NT 5.0; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Thanks very much Matt! Those articles sound very helpful - I guess I didn't look hard enough to find them. Will try them tonight after my getting-rid-of-old-junk-computers binge to free up workbench space for a suitable test computer. Vic
100% CPU usage occurred most often toward the end of the working day when busy trying to print on-line postage. We don't have any memory-consuming plugins but according to the knowledge base articles Firefox memory usage can gradually increase during the day even if you do nothing. It seems that may be the problem so we close and restart Firefox more often now as that usually fixes the problem. However, if we get stuck on a particular website update that causes the CPU to to go 100%, we can always start Firefox without previous tabs so the update will stop, or simply use a different browser until we have time to let the computer play games with itself. So our workaround of restarting Firefox turns out to be the final solution (until we find something better - will post it if we do). Vic