Closed Bug 300999 Opened 20 years ago Closed 19 years ago

Firefox regrabs memory and doesn't let go after closing

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 239223

People

(Reporter: winsnomore, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 2.0.50215) Build Identifier: Open firefox .. it goes to 126Meg memory usage .. minimize it, it goes to about 2Meg. Close firefox . Firefox window closes but the task stays and starts growing .. grabs 77Meg memory and keeps using 30% cpu Reproducible: Always Steps to Reproduce: 1. Start firefox 2. Minimix the window 3. reactivate window .. and then exit firefox Actual Results: firefox window closes, but the task stays and starts grabbing memory and hogs 70+Mbyte of memory and 30% CPU .. Expected Results: task should disappear and shouldn't be using memory This is a major problem .. .forcing me to restart my PC every few days.
What build of firefox are you using? Please test with a current trunk build from ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
I have this problem with the latest Deerpark Alpha 2. From 7/20/2005. The usage climbs to like 140MB!!!! I am sorry guys, but that is kinda ridiculous!
Sounds a lot like bug 249469.
firefox 1.5 beta 2 Win XP Professional after closing the firefox window, the task stays in memory. when reopening firefox, a new task is added Reproducible: always (as many tasks as you want) max memory used: around 30 MB expected behavior: task (process) should free memory, after closing firefox
this happens to me as well on a win xp sp2 system. I tried to test this on the ffx rc2 build, with a new profile in safe mode. I opened a web site with wallpapers, opened 30+ tabs through it so taht mem usage shot to 100+. Upon closing all the tabs and opening the google page...mem usage dropped to 92 mb. But 92 mb for the google start page??? Minimising drops the memory to mormal, but maximise it again..and it again climbs to 92 mb. Its surprising that such a bug exists, and even more surprising that all the people who meet with this bug are treated with criticism.
Blocks: ghostproc
Ugh; for me, now w/FF1.5.0.2, minimizing does not even free RAM. The only way now I can free RAM is to run a forcible RAM-grabbing utility [e.g., rambooster]. This now has become worse than moz 1.7.12(!).
Yes, I have also have problems with firefox and my computer's RAM. Normaly, when first time using Firefox it use approx 20 MB RAM, but as using it rise till 100 MB and so one. One day I didn't understand what is happening why my computer is slow and checked Tas Manager - I was shocked Firefox was used 760 MB of RAM!!! And from that day I very offen check what Firefox is doing and when RAM is used 100 MB I close all Firefox and open new which uses in begining 20 MB of RAM. And this is all time. I'm starting to think may be not to use firefox, till this problem will be solved as I'm using firefox almoust 3 years.
To anyone who commented: If you read the comment 0, this bug is not about a memory leak, but about not exiting on shutdown. And even if it were about a memory leak, you should have read https://bugzilla.mozilla.org/page.cgi?id=etiquette.html before (and/or instead of) commenting. Since the original reporter is unavailable and no new information is given in comment 0, I'm going to dupe this against bug 239223. *** This bug has been marked as a duplicate of 239223 ***
No longer blocks: ghostproc
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.