Closed
Bug 467693
Opened 16 years ago
Closed 14 years ago
Leak nsStringBuffer with coincidental property name match
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: memory-leak, testcase)
Attachments
(2 files)
The two lines in function boom() seem independent, but together they make Firefox leak an nsStringBuffer. Maybe it has something to do with nsIWebNavigationInfo (on the second line) having a property called "UNSUPPORTED", which is coincidentally also the tagName of the element on the first line. The balance tree makes me suspect that xpc quickstubs are acting up.
|
Reporter | |
Comment 1•16 years ago
|
||
|
||
Comment 2•16 years ago
|
||
Does this leak anything else? Or just the string buffer? Could be the JSString leaking.
|
|
Reporter | |
Comment 3•16 years ago
|
||
The nsStringBuffer is the only trace-refcnt-instrumented object that leaks.
|
|
Reporter | |
Comment 4•14 years ago
|
||
Still happens on trunk.
|
|
||
Comment 5•14 years ago
|
||
This seems to have been fixed. Doesn't leak for me on trunk on OS X. Jesse, can you confirm?
|
|
Reporter | |
Comment 6•14 years ago
|
||
WFM. Yay!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
|
|
Reporter | |
Comment 7•14 years ago
|
||
Crashtest: http://hg.mozilla.org/mozilla-central/rev/688a6b1a5aa3
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•