Closed Bug 475453 Opened 16 years ago Closed 7 years ago

Categories

(Core :: General, defect)

1.9.1 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak, testcase)

Attachments

(2 files)

Attached file leak log (deleted) —
found during the topsite test and reproduced local.

Steps to reproduce:
-> Load http://www.megajogos.com.br
-> Wait till the site is loaded (to prevent a shutdown leak)
-> Close Firefox
--> Leak

0 TOTAL                                          22    24778  1706460      759 ( 2910.05 +/-  2190.90)  2331484      654 ( 1551.46 +/-  2561.02)
Attached file testcase (deleted) —
Flags: in-testsuite?
Flags: blocking1.9.2?
Flags: blocking1.9.1?
Keywords: testcase
A lot of this is being kept alive because places is being held onto.
In fact, because we are leaking 32 mozStorageStatements, which I suspect all are related to places, that means we either aren't receiving the proper shutdown notification, or this code isn't being called:
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/src/nsPlacesDBFlush.js#112
(finalizeInternalStatements would free things up)
Shutdown leaks don't block unless someone can tell me why.
Flags: blocking1.9.1? → blocking1.9.1-
No longer depends on: sisyphus-tracking
Flags: blocking1.9.2? → blocking1.9.2-
Filter on QUANTUMLEAK
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: