Windows Firefox 2.0.0.1

2.0 was good, now they slam 0.1 in my face and when I upgraded, I noticed one thing and one thing only.

omg, its slow.

I can't even open up my bookmarks.

anyone else have this problem?

 

Agreed. Resource hog. 42,204 K right now. I can open bookmarks fine and run it fine, provided I don't strain it. Multi-tasking with it open will cripple my machine.

 

56,312K right now. Not noticed a thing different.

 

yeah. I noticed this yesterday. after upgrading I had nothing but trouble the rest of the day with it locking up 3 or 4 times in a couple hours. I left my computer on over night and come in this morning to find it's locked up again when I'd done nothing to it overnight and it was working fine when I left. current memory usage is 65.900
err, in the time it took to write this post, it's constantly going up. it's gone from around 63k to now 66.7k

 

Hmmm atm mine eats up 74.000 to 75.000 ,
allthough I dont "feel" any diffrens than before upgrading.

edit:/I just took another look at the taskmanager and it went up to 82.908...WTF?

 

Memory usage isn't a very useful measure. You need to combine it with pagefile usage as well. You can see individual virtual memory usage for each process by ticking the column in task manager. Currently I'm using Firefox 1.5.0.9 (just updated itself today) and the memory + virtual memory usage is at 197,000K which I'm pretty sure is above average for having just 3 tabs open. Maybe the upgrade from 1.5.0.8 to 1.5.0.9 has this same memory problem as 2.0.0.1.

 

Firefox has always been a resource hog, but only for Windows it seems, when I've used it on OSX and Linux at uni it loads instantly. Wheren't they supposed to have fixed this in 2.0 anyway?

 

If they were, I don't think they did a good job.

 

heh, i gave up on fireflop and use opera now =D no problems at all

 

Works fine for me - all my extensions, bookmarks, etc. I still won't use anything else.

Edit: 5 open tabs, 30,000K RAM memory usage, 90,000K Page File usage.

 

Working fine for me also, even at 125,000 K.

(edit: Just closed and open firefox and now I'am sitting at 49,000 k. But coming here to bit tech cost me 15,000 K.)

 

I don't think the issue is whether or not Firefox runs ok. That depends on how much RAM you have and how many other programs you have running. The issue is whether or not Firefox has suddenly become even more memory hungry or somehow developed memory leaks.

My memory usage (including virtual memory) has gone up to about 220,000K now after running it all day. 6 tabs are open at the moment although closing tabs never seems to have any beneficial effect for some reason. Also bit-tech's flash adverts seem to be eating up 100% of the CPU at the moment and I'm not sure if that's always been the case either.

 

I noticed FF being really slow last night, but I attributed it to the fact that I was severely taxing my connection with network file transfers at the time. I'll have to keep watching, to see if it was FF or just because of the multitasking.

And I don't really care how much RAM the thing uses - I have the RAM for a reason, and I don't leave FF open unless I'm actively using it, so it's not likely something else will be needing the memory.

 

The solution.

 

NVM

 

Good, work, Ramble. You're so much cooler than all the people on Slashdot who scream "switch to Linux" every time someone complains about a problem with Windows. Is it even remotely possible that we like Firefox for dozens of reasons and we just happen to be irritated by a single issue? On the other hand, I'm sure there isn't a single thing wrong with Opera, such as having even less widespread compatibility than Firefox and sometimes rendering nested navigation menus incorrectly.

 

well not to point out the obvious but i think that firefox has a memory leak. when i read this i started to notice the pattern, the longer you have it open the more ram it eats.

 

GASP!!
Firefox is like a car, the more you have your car on the more gas it guzzles.

 

553360K for me, that's about 60% and it's running just fine, although I've found every once in awhile it will come to a grinding halt and take forever...

 

i dont think its about how well it runs while its eating our ram, i think were talking about the fact that it does eat it.