Originally reported on Google Code with ID 2372
Per the comment on issue 2187, I'm opening a new case with the details of
what I found despite a fix being posted for 2187. This might be unrelated
but it seems to have some overlap.
I've upgraded to 1.5a26 and still see the issue.
Original post:
-------------------------------------
Not so sure about that. I've been seeing this memory leak issue for some
time. The
fact that you narrowed it down to being related to the Errors generated
makes a lot
of sense. For instance, before the 1.5a25 release which I just downloaded
to see if
it finally fixed the issue, I would get the memory leak a lot faster when
developing
against a local site I'm running with Windows Authentication. FF seems to be
generating 401 errors because it's not attempting to use credentials on the
first two
attempts before it finally does and generates a successful hit.
So for my app with a bunch of Ajax hits per page, it adds up fast. As I was
working
tonight, I managed to go from 70MB (90MB peak) on FF 3.5.3 with the 1.4
version of
Firebug to 210MB (250MB peak) in a matter of minutes (something like 15-20
minutes).
Once I upgraded to the 1.5a25 build, I managed to get to 150MB (200MB peak)
but it
took a bit longer (more like 30 mins). Keep in mind, this was with one
window and a
single tab in that window running. Outside of Aviary, FireCookie,
WebDeveloper, and
the RealPlayer download add-on, Firebug is the only other add-on installed and
active. There are a few more that are installed but disabled.
FYI, when I ran the browser for a while with Firebug disabled (the other
add-ons
still there), memory stayed around 70-90MB in use.
Right now, with two windows open (the window I'm using to enter this report
plus the
original window I was developing and testing with), I'm at 157MB in use. If
I hit
refresh in the window I was developing with (the one with all those Ajax
errors),
it'll add an additional 2-5MB of memory to Firefox's allocation and not let
it go.
The Peak also increases (there's a roughly 45-50MB gap between peak and
actual memory
usage). I just refreshed (again, two windows are open though, one tab each) and
memory usage went up to 168MB.
One more time and memory's at 170MB. One more time for science! 171MB. And
yes, I've
waited for minutes on end and the memory isn't deallocated. There's a 0.5MB
fluctuation (deallocates, reallocates) but that's it.
Restarting the browser clears it and starts the process all over.
Again, this is an Ajax heavy site (I count 9 distinct calls) on a development
workstation. For those 9 distinct calls, I'm seeing 3 hits per call. Two
fail with a
401 unauthorized error and the third succeeds.
Let me know if there's anything else I can try that won't be too
disruptive. I've
still got to get work done here. :)
Reported by ken.nakai on 2009-10-10 03:28:33
该提问来源于开源项目：firebug/firebug
