Created attachment 351100 [details] testcase 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.
Does this leak anything else? Or just the string buffer? Could be the JSString leaking.
The nsStringBuffer is the only trace-refcnt-instrumented object that leaks.
Still happens on trunk.
This seems to have been fixed. Doesn't leak for me on trunk on OS X. Jesse, can you confirm?
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.