Closed Bug 573190 Opened 15 years ago Closed 14 years ago

Leak memberName in XPCNativeMember::Resolve

Categories

(Core :: XPConnect, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: memory-leak, valgrind)

Attachments

(1 file)

Attached file valgrind output
This is one of the most frequent leaks reported by Valgrind. I hit it over 100 times just starting up and shutting down.
"The array returned by JS_GetStringBytes or JS_GetStringBytesZ is automatically freed when str is finalized by the JavaScript garbage collection mechanism. The application must not modify the contents of the array." So I guess the question is why the string didn't get GCed.
mrbkap looked at this a bit. The only leaked objects are strings that are "interned atoms".
WFM. Might be related to bug 655435 somehow.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: