Closed Bug 326635 Opened 19 years ago Closed 19 years ago

node.setUserData("foo", anyNode, null) leaks GC roots and DOMWindows

Categories

(Core :: DOM: Core & HTML, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 324871

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: memory-leak, testcase)

Attachments

(1 file)

JS engine warning: leaking GC root 'XPCVariant::mJSVal' at 0x2459f294
JS engine warning: 1 GC root remains after destroying the JSRuntime.
                   This root may point to freed memory. Objects reachable
                   through it have not been finalized.
Attached file testcase

*** This bug has been marked as a duplicate of 324871 ***
Status: NEW → RESOLVED
Closed: 19 years ago
No longer depends on: 324871
Resolution: --- → DUPLICATE
So I actually don't immediately see why the document is being kept alive in this case, although I suspect from the warning that fixing this requires treating XPCVariant like bug 241518 treated nsXPCWrappedJS -- by marking rather than rooting.
This appears to be a bug that was created since the 1.8 branch, since bug 326635 landed after the branch; therefore maybe it can wait for graydon's cycle collector to fix the problem.
Flags: needinfo?(general)
Flags: needinfo?(general)
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: