Closed
Bug 421312
Opened 16 years ago
Closed 14 years ago
Important leak at each XMLHttpRequest
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: WSourdeau, Unassigned)
References
()
Details
(Whiteboard: [CLOSEME 2010-11-01])
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8.1.12) Gecko/20080129 Iceweasel/2.0.0.12 (Debian-2.0.0.12-1) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8.1.12) Gecko/20080129 Iceweasel/2.0.0.12 (Debian-2.0.0.12-1) (To access the page above, use "sogo1" for username and password.) The SOGo mail module enables automatic refreshes of the current mailbox. The interval is user-configurable but defaults to 5 minutes. When you let the module page open all the night, Firefox leaks so much that it has to be killed and takes 1 minute or so to completely free its process space. I have checked and rechecked and rechecked what could cause a leak in my code and could not find anything. Every request takes between 0.5 and 2.0Kb of RAM and never gives it back. Reproducible: Always Steps to Reproduce: login to the page wait for your instance to consume all your memory or press "refresh" (which call the exact same methods) and see how the memory usage inscreases Actual Results: Memory usage increases
Reporter | ||
Comment 1•16 years ago
|
||
Any news regarding this issue?
Comment 2•14 years ago
|
||
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Comment 3•14 years ago
|
||
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•