This post originated from an RSS feed registered with .NET Buzz
by Raymond Lewallen.
Original Post: FireFox - The Hungry-Hungry Hippo?
Feed Title: Raymond Lewallen
Feed URL: /error.htm?aspxerrorpath=/blogs/raymond.lewallen/rss.aspx
Feed Description: Patterns and Practices, OOP, .Net and Sql
Firefox! Please! I love you so much, please relenquish
your iron grip on my resources, as you are rendering my computer
useless.
I like to have just one browser open, and sometimes get up to about
10 tabs open in that browser. Its becoming more common that
Firefox (Iâm using 1.0.7) locks up and I have to kill it. This
time, I had 4 tabs open, none of which were running anything dynamic
that _should_ cause the CPU usage for the browser to remain high.
I didnât screen shot what the resources were like before I had to kill
it, but I can tell you it was running 100% for the longest time, using
289MB of memory and 371MB of virtual memory. Total that up kids,
that a whopping 660MB of memory! The high memory usage seems to
be the norm for FireFox, when used the way I use it (one instance,
mutliple tabs).
Why on earth does my browser feel the need to consume that much
memory? I have the memory available, but still. Hereâs the
screenshot of my task manager directly after having to kill the
firefox.exe process. You can see by the history where its just
sucking up the CPU, and its been doing this more and more often.
Has anybody else been experiencing their FireFox taking on the
persona of a Hungry-Hungry Hippo(TM)?
It seems to do this randomly, not
when I'm visiting a particular site of sets of sites. Its not
picky about the sites I visit or the number of tabs I have open, it
just likes to lock-up. Sometimes, I just wait it out, and after
about 5 minutes or so, the majority of the time is returns back to
reality and frees up my computer. I have yet to figure out what
it could be doing and what is causing it to behave this way.
I'm going to upgrade to 1.5 to see if it helps out.
Update: I upgraded to 1.5, and now half of my add-ons and plug-ins don't work anymore. But we'll see how it goes with the resource usage.
Previous Topic
