558733 - memory leak when reloading javascript scripts, caused by Firebug

Status: RESOLVED DUPLICATE of bug 669730

(Core :: JavaScript Engine, defect)

Description

[Angelo Borsotti]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

when the attached page is reloaded, the memory used by Firefox grows.
Reloading repeatedly the page the memory is sometimes released, but
not entirely so that the net effect is a steady growth. The page contains
barely only javascript code consisting of functions and variables.
I have reduced the file as I could to show the problem. With the actual
file, Firefix grows to half a Gb in 2-3 hours.

Reproducible: Always

Steps to Reproduce:
1.open the page
2.open the task manager and note the memory occupation of Firefox
3.reload repeatedly the page
Actual Results:  
the memory grows from 37Mb to 47Mb after 10-15 times the page has
been reloaded

Expected Results:  
no growth of memory on average

Comment 1

[Angelo Borsotti]

Attachment: page that shows the memory leak on javascript

Comment 2

[Jo Hermans]

I'm not seeing a memory increase, neither in Task Manager (which is bad way to measure memory leaks) or in about:memory (correct way)

Do you see it in Safe Mode (without add-ons ?)
http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 3

[Mike Shaver (:shaver emeritus)]

Task Manager for Private Working Set is more reliable than about:memory for JS-related things, until we fix some accounting bugs.

Safe Mode also disables the JIT, but it's good data to get.

Comment 4

[Angelo Borsotti]

I have opened the same page with Safe Mode, and have not seen any leak
with it. about:memory does not report leaks, not even when running
without Safe Mode (in which I am pretty sure there is a leak because
the memory reported by the task manager and also by the system monitoring
are somehow inaccurate, but not that much).
I suspect the leak could be due to Firebug, and I am filing a problem
report to it.

Comment 5

[Mike Shaver (:shaver emeritus)]

Are you running the most recent Firebug?  I believe they recently fixed a memory leak.

Comment 6

[Angelo Borsotti]

Yes, I do. I have subscribed to receive notification of Firebug updates,
and install them as soon as they are released.

Comment 7

[Marco Castelluccio [:marco]]

Any news?

Comment 8

[Nicholas Nethercote [inactive]]

Even more Firebug leaks have been fixed, but some remain.  I'm going to dup this to bug 669730, which is a remaining one.