Closed Bug 666105 Opened 14 years ago Closed 14 years ago

Leak in one of these four sites?

Categories

(Core :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: n.nethercote, Unassigned)

References

Details

(Whiteboard: [MemShrink:P2])

Firefox 4 uses 1.5 GB of memory actually on my system. Here is what I found at about:memory (attached screenshot). This is a spin off of bug 645633 comment 8; that bug has become a mess. René Schwarz got large, increasing memory usage with the following tabs: Runtime approx. 10 hours, 6 tabs permanently in background open (Panorama): <http://www.linuxlibertine.org/index.php?id=86> <http://test.elmastudio.de/> <http://www.drweb.de/magazin/html5-ueberblick/> <http://net.tutsplus.com/tutorials/html-css-techniques/html-5-and-css-3-the-techniques-youll-soon-be-using/> <http://www.saechsdsb.de/ipmask> <http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF> After closing five background tabs (Panorama) yesterday, Firefox 4 hasn't increased its memory size during the night (approx. 9 hours). The closed tabs were <http://www.linuxlibertine.org/index.php?id=86> <http://test.elmastudio.de/> <http://www.drweb.de/magazin/html5-ueberblick/> <http://net.tutsplus.com/tutorials/html-css-techniques/html-5-and-css-3-the-techniques-youll-soon-be-using/> So I suppose that one of them has been the reason for the memory leak.
René: it's possible that bug 656120 has fixed this problem. Can you please try a nightly build (nightly.mozilla.org) and let us know if it has been fixed? Thanks.
MemShrink has improved things greatly since FF4, there's a good chance this has been fixed in FF7 or later. Combine that with the lack of additional info, and I'm going to close this.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Hello Nicholas, I've tested the issue again and it seems that the problem is gone.
Thanks for the update! Good to know.
You need to log in before you can comment on or make changes to this bug.