Updated to FF 2.0.0.2 yesterday, and the first thing I did was to reinstall FCF 0.9.3.1 to see if there was any improvement on the problem that was discussed here...
http://forums.mozillazine.org/viewtopic.php?t=502593
...and I'm happy to report that, after FF ran all night (8 hours) minimized idle on a simple page with no flash (www.google.com), the CPU usage remained at 0% and memory usage increased by only 4,000K (24,000K to 28,000K). My other extensions (IEtab 1.3.1.20070126, DownThemAll 0.9.9.7) are still installed as they were during the FF 2.0.0.1 problem.
I find it interesting to note that when problems with extensions occur after a FF update, the general opinion usually seems to be that it is the extension (and not FF) that is broken. However, since FCF is unchanged and the problem went away with FF 2.0.0.2, this appears to indicate that it was FF 2.0.0.1 which was broken.
wolleybus
Firefox 2.0.0.2 Fixes Forecastfox 0.9.3.1 Memory/CPU Problem
-
- Guest
-
- Posts: 3483
- Joined: November 4th, 2002, 10:47 pm
- Location: Ann Arbor, Michigan
- Contact: