Linked by diegocg on Sat 28th Apr 2007 23:15 UTC
Thread beginning with comment 235157
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
I use Firefox for days without restarting, and the memory usage does rise higher until I eventually have to restart it. The thing is, I've actually found that IE7 is even worse. I haven't used it continuously to see if it leaks memory as much, but when I open 10-15 tabs in IE7 and the same in Firefox, IE7 is using considerably more memory.
Aye? What version are you running? right now 4 tabs, and it uses 72MB is total, which is a far sight less than what I experienced with Firefox.
Firefox isn't just a memory bloater on Windows, use Konqueror on *NIX and compare it to Firefox, for instance; compare Epiphany to Firefox too.
I can't say I completely agree or disagree with this - I don't think they focus enough on those things, but I don't think it's fair to say they don't care about them either. I think there have been a lot of changes in this area that will be showing up in Firefox 3, ironically because they didn't want to make huge changes in 2 for fear of making things unstable.
But what I want aren't big changes, but fixing up long standing bugs which piss end users off; these can be made right through the 2.x cycle with no impact on the over all stability of the application.
Yes, crawling through code and fixing up stupid coding mistakes can be as painful as being kicked in the goolies, but its better to fix them up now before they cause bigger problems later on.






Member since:
2005-10-13
I use Firefox for days without restarting, and the memory usage does rise higher until I eventually have to restart it. The thing is, I've actually found that IE7 is even worse. I haven't used it continuously to see if it leaks memory as much, but when I open 10-15 tabs in IE7 and the same in Firefox, IE7 is using considerably more memory.
There are tools out there to detected memory leaks, what I see the problem is that Mozilla developers are more concerned about adding features than trying to get the underlying technological foundation secure, stable and reliable.
I can't say I completely agree or disagree with this - I don't think they focus enough on those things, but I don't think it's fair to say they don't care about them either. I think there have been a lot of changes in this area that will be showing up in Firefox 3, ironically because they didn't want to make huge changes in 2 for fear of making things unstable.