User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98) Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 a RAM leak of several megabytes caused by loading Firefox 0.9.3, letting homepage load (doesn't matter what homepage is) and then exiting the client. I'm not sure where it is in the code as I haven't poked around much/at all, but it is very reproduceable on Win98SE with Firefox 0.9.3 and homepage set to www.hothardware.com/forum/ - works every time if only one instance of Firefox is loaded but a second copy doesn't leak memory if loaded and closed while the first copy is still loaded. Load/unload with www.hothardware.com/forum/ lost 2027520 bytes of RAM in one test (amount lost is variable, runs anywhere from ~300kB in one test to over 8MB seemingly at random), loading two copies and closing both seems to randomly either lose only the amount of RAM for one copy or gains back some lost memory. See screenshot of System Manager at: http://comphobbyist.8k.com/downloads/mozilla%20memory%20leaks.png (simple load/unload in all cases, loaded and unloaded FireFox twice and IE6 3x) Reproducible: Always Steps to Reproduce: 1. Fully update Win98SE - may not be critical but is a good idea 2. Start System Monitor in Start Menu -> Programs -> Accessories -> System Tools -> System Monitor and add "Free physical memory" as an item to graph 3. Start Mozilla Firefox 0.9.3 4. Allow homepage to load 5. Close Firefox using the Exit button in the upper right-hand corner 6. Alt+Tab back to the System Monitor and notice that free RAM is constant, spikes downward and load, then spikes back up on exit - but not as far as on load. Several megabytes were lost each and every time I did this on my system - if I clicked several links before closing it lost a couple more megabytes. Actual Results: Much RAM leaked - described results above Expected Results: Not leaked memory on startup/exit :( Bug still occurs in default install as non-default browser, standard theme and configuration

Isn't it the operating system's job to reclaim memory after an application has exited? INVALID?

(a derivate of) quickstart at work?

*** This bug has been marked as a duplicate of 249469 ***