The extraordinarily severe Firefox 4.0.1 memory leak issue(s) (at least as seen under Windows, but also other OSs that are affected), urgently needs to be formally addres… (xem thêm)
The extraordinarily severe Firefox 4.0.1 memory leak issue(s) (at least as seen under Windows, but also other OSs that are affected), urgently needs to be formally addressed by official or officially delegated Mozilla technical experts, and all effective solutions, work-arounds, or troubleshooting tips for this precise situation should be provided in a single, centralized location. This is necessary because, as of now, there are a very considerable number of different posts, alleged solutions, and other strange suggestions, many of which either contradict each other or are ineffective or entirely wrong-headed in the first place.
A staggering number of FF 4 users are reporting this often astonishingly severe memory leak problem, while others who might justly be described as Firefox 4 apologists (well-intentioned, I'm sure) either deny the problem exists or offers suggestions or strategies that are either: (1) beyond the technical ken of most users; (2) would require many weeks of painstaking trial and error (such as enabling only one add-on or extension at a time, which is far more complex than one might at first think because most add-ons have numerous options which could very well affect the outcomes depending on their settings and/or depending on which web sites the user browses to, and/or depend on subtle interactions with other add-ons such that the problem would not appear if they were disabled at the time, etc., etc., etc.). Considering all these complexities, expecting users to "heal themselves" is both absurd and arguably arrogant as well.
I will provide more information in the other fields of this form, but I wish first to identify the extreme nature of this memory leak issue, which began only after updating from the latest version of FF 3: When I launch FF 4 from a saved session with several tabs already opened, it consumes no more than around 200 MB or RAM. After it finishes loading, with NO user interaction whatsoever (I just let it sit there, untouched), I bring up a process monitor and watch as Firefox 4 (just the .exe, not the container process) acquires at least 12 additional megabytes and often around 50 additional megabytes PER SECOND!
Yes, 12-50 megabytes of additional memory PER SECOND!
And I'm not doing anything at all.
Within ten minutes -- even while doing nothing whatsoever with FF -- FF 4's RAM footprint reaches about 1.5 GB (of 2.3 GB available to XP out of 4 GB physical RAM), and after 20-30 minutes it consumes all available RAM and thus VM usage soars, resulting in a dramatic increase in disk I/O.
This is, shall we say, unacceptable. FF 3.6.x had no such issue at all, no matter how many tabs were open and with almost exactly the same add-ons installed.
I realize that Mozilla is primarily a volunteer project, and I tremendously respect and profoundly admire every last one of you folks. And Firefox IS, in my view, the finest web browser in existence. I absolutely do NOT denigrate or minimize the enormous efforts you all have undertaken or the value of your products! That I ask for still more effort and for consolidation of your findings suggests just how highly I value these efforts as well as the wonderful fruits of your products rather than the reverse!
Thank you all