Closed
Bug 415112
Opened 17 years ago
Closed 17 years ago
Memory leak of nsInstantiationNode and AtomImpl, using datasources, template, ref and observes
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Assigned: sicking)
Details
(Keywords: memory-leak, testcase)
Attachments
(1 file)
|
327 bytes,
application/vnd.mozilla.xul+xml
|
Details |
See testcase, I see these leaks occuring in current debug trunk build with trace-malloc enabled:
== BloatView: ALL (cumulative) LEAK STATISTICS
|<----------------Class--------------->|<-----Bytes------>|<----------------Objects---------------->|<--------------References-------------->|
Per-Inst Leaked Total Rem Mean StdDev Total Rem Mean StdDev
0 TOTAL 23 32 543287 2 ( 1129.32 +/- 1459.34) 1179164 1 ( 1559.98 +/- 2412.36)
1 AtomImpl 20 20 1300 1 ( 619.73 +/- 353.08) 14580 1 ( 2919.79 +/- 1216.67)
423 nsInstantiationNode 12 12 1 1 ( 1.00 +/- 0.00) 0 0 ( 0.00 +/- 0.00)
|
Assignee | |
Comment 1•17 years ago
|
||
This is bad, but I think it won't bite users too much since XUL is hardly used on the web. Chrome might still leak though so we should definitely look into it.
Assignee: jag → jonas
Flags: blocking1.9+
Priority: -- → P3
Flags: wanted1.9+
Flags: blocking1.9-
|
||
Updated•17 years ago
|
Flags: tracking1.9+
WFM today. Martijn, can you confirm?
|
Reporter | |
Comment 3•17 years ago
|
||
yes, wfm too.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•