Linked by Thom Holwerda on Thu 13th Mar 2008 20:41 UTC, submitted by RJop
"While Firefox 2 used less memory than it's predecessor, Firefox 1.5, we intentionally restricted the number of changes to the Gecko platform (Gecko 1.8.1 was only slightly different than Gecko 1.8) on which Firefox was built. However, while the majority of people were working on Firefox 2/Gecko 1.8.1, others of us were already ripping into the platform that Firefox 3 was to be built on: Gecko 1.9. We've made more significant changes to the platform than I can count, including many to reduce our memory footprint. The result has been dramatic."
Thread beginning with comment 304987
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2006-03-12
Member since:2005-07-06
It comes nearer to the name and shame time 
hope you have tried it yet btw after your last misinformed comment On firefox another over 70 memory leaks have been plugged.
Can't wait till launch I need to start getting my quotes ready.
hope you have tried it yet btw after your last misinformed comment On firefox another over 70 memory leaks have been plugged.
Can't wait till launch I need to start getting my quotes ready.
I never denied the fact that there have been improvements, the problem I have is that they're just going to sit around and stop improving it after the dust settles over memory leaks. The tracking of memory leaks should be an on going project, and they should be part of the routine updates in future releases.
The only reason they've actually done a damn thing about memory leaks was the pissing and moaning from people like me; screaming from the rafters over the crap memory management. Now that they've fixed *some* but not all of the memory issues, are we going to see them de-allocate resources now that the majority of alarmists like me have chosen to go silent? that is the issue I have.
I want to see Firefox succeed, but I have a problem with organisations who, after one achievement, they lack the motivation to keep moving forward; if Firefox developers were *truly* committed to the memory leak issue, they would assemble a auditing and benchmarking team whose sole job is to fix memory related issues. When I see that happen, and when I see the fixes at the top of the list to be merged, then I'll believe that they're committed to it for the long term.
Member since:
2005-07-06
But I have a feeling that after Firefox 3.0 is released, there will be no further effort to improve the memory situation or the lack of proper integration on non-Windows platforms. It annoys me for something which talks about being the product of opensource, such little resources are actually used by Mozilla to improving the experience on alternative platforms.
I know I sound bitter but I've been waiting for over 2 1/2 years for Mac OS Aqua form buttons to *FINALLY* appear in the Mac OS X build, how long before we start seeing an effort for proper integration with Mac OS X beyond the superficial?