Closed
Bug 514807
Opened 15 years ago
Closed 14 years ago
[HTML5] Tinderbox leaks nsGenericElement+ with html5.enable true
Categories
(Core :: DOM: HTML Parser, defect, P1)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
Details
(Keywords: memory-leak)
Loading http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox leaks nsGenericElement and more (as shown by trace-refcnt), but only if html5.enable is true.
Updated•15 years ago
|
Summary: Tinderbox leaks nsGenericElement+ with html5.enable true → [HTML5] Tinderbox leaks nsGenericElement+ with html5.enable true
Updated•15 years ago
|
Priority: -- → P1
Comment 1•15 years ago
|
||
I don't see the leak anymore with my patch queue applied, but NS_LogAddRef_P asserts a lot: NS_ASSERTION(serialno != 0, "Serial number requested for unrecognized pointer! " "Are you memmoving a refcounted object?");
Comment 2•15 years ago
|
||
Also leaked when nsGenericElement leaks: 89 nsHtml5AttributeName 16 9296 581 581 ( 291.00 +/- 167.86) 0 0 ( 0.00 +/- 0.00) 90 nsHtml5ElementName 28 10948 391 391 ( 196.00 +/- 113.02) 0 0 ( 0.00 +/- 0.00) 91 nsHtml5HtmlAttributes 24 24 1 1 ( 1.00 +/- 0.00) 0 0 ( 0.00 +/- 0.00) Which looks like nsHtml5Module never gets a shutdown call, which would mean the layout module isn't shutting down properly.
Comment 3•14 years ago
|
||
Marking WFM per comment #1, since the assertions fire with the old parser, too (filed as bug 548258).
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•14 years ago
|
||
WFM, no leak on trunk with html5.enable true.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•