Leak nsStringBuffer with coincidental property name match

RESOLVED WORKSFORME

Status

()

Core
XPConnect
--
minor
RESOLVED WORKSFORME
9 years ago
7 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

(Blocks: 2 bugs, {mlk, testcase})

Trunk
x86
Mac OS X
mlk, testcase
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

9 years ago
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.
(Reporter)

Comment 1

9 years ago
Created attachment 351101 [details]
balance tree
Does this leak anything else? Or just the string buffer? Could be the JSString leaking.
(Reporter)

Comment 3

9 years ago
The nsStringBuffer is the only trace-refcnt-instrumented object that leaks.
(Reporter)

Comment 4

8 years ago
Still happens on trunk.
This seems to have been fixed. Doesn't leak for me on trunk on OS X. Jesse, can you confirm?
(Reporter)

Comment 6

7 years ago
WFM. Yay!
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 7

7 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.