Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How to track Memory Leaks in 3.6.8?

  • 13 replies
  • 118 have this problem
  • 4 views
  • Last reply by maquidkzy

more options

I've been noticing for several updates now that I seem to be getting major memory leaks. Firefox starts off around 1-200,000 K memory usage in task manager, but within a few hours it will be past 800,000 K. Now, the things I've seen so far talk about disabling plugins and all to find the problem, but this doesn't happen immediately, so disabling things one by one isn't very feasible. How can i track the memory leak to a specific plugin, or else make it leak much, much faster so I can do the one by one thing?

This happened

Every time Firefox opened

== A few updates ago

I've been noticing for several updates now that I seem to be getting major memory leaks. Firefox starts off around 1-200,000 K memory usage in task manager, but within a few hours it will be past 800,000 K. Now, the things I've seen so far talk about disabling plugins and all to find the problem, but this doesn't happen immediately, so disabling things one by one isn't very feasible. How can i track the memory leak to a specific plugin, or else make it leak much, much faster so I can do the one by one thing? == This happened == Every time Firefox opened == A few updates ago

All Replies (13)

more options

This happens to me all the time... After a days work with firefox open all the time, memory usage keeps increasing steadily. The included screenshot shows memory usage at noon. (Sometimes it even gets to 1.300.000 kb and then freezes)

I keep a lot of tabs open all the time, but by closing a tab, memory usage doesn't seem to go down. I guess that the memory leak might be situated somewhere around the code of tabhandling.

If you close firefox however and restart it with the same tabs opened, memory usage is usually a lot lower. (around 50000 kb to 130000 kb)

I hope this issue will be fixed in the upcoming versions of firefox.

more options

Same problem, same symptoms...

more options

If compare our plugins Adobe Shockwave is reason of memory leak. But I think that it's a firefox problem.

more options

Also firefox version 3.6.3. Windows XP SP3

more options

See if this extension helps you. Leak Monitor https://addons.mozilla.org/en-US/firefox/addon/2490/

more options

Well, It just has taken a turn for the worse... In the attached screenshot you can see firefox took 1.123.112kb out of my memory at which point the GUI became unresponsive. This has actually happened before, but not as soon...

I had 18 tabs open (but at the moment I have all of them opened again after a restart of firefox and it takes 143.988 kb at this very moment, which still is a lot actually). My computer has 4gb RAM-memory of which 46% is in use at the moment according to windows task manager.

It would be great if the whole tabstructure and maybe the garbage collector for the TraceMonkey javascript engine was reviewed... This might point out where the memory leaks are located.

more options

btw, I have used the leak monitor and it annoyed me a lot, because all of the leak monitor alertboxes I encountered, so I eventually turned it off...

more options

Maybe is a problem of the most brausers which open new tabs in one process (in chrome it isn't a problem, one tab - one process - 20 Mb :) ). I talk that, because I have the same problem in opera when number of tabs is big.

more options

sorry "browsers"

more options

Just try to turn off java deployment toolkit plugin (NPRuntime Script Plug-in Library for Java(TM) Deploy), some versions of it causing memory leaks.

more options

having the same problem, after a couple of hours, its suck up 600 megs or Ram.

more options

Same problem here. Reminds me of the bad version streak in the 3.5.x period.

more options

Windows XP SP2, FF 3.6.8

I have the same problem, same symptoms also. But in my case I think this maybe cause from some web page that using AJAX that I opened for a long time. For instance, facebook chat.

Modified by maquidkzy