12115 - [mlk] -size of leak?- XUL elements leak after being involved in an event dispatch

Status: VERIFIED DUPLICATE of bug 18066

(Core :: XUL, defect, P3)

Description

[Chris Waterson]

To reproduce, install attached test file as "leak.xul".

1. Start viewer.
2. Open test file.
3. Set breakpoint in nsBookmarksService::Release()
4. Click on the titledbutton ONCE.
5. Click "Back" button.

Note that the bookmarks service is _never_ released. Remove the "onclick"
handler; restart viewer; you should see the bookmarks service be released
(although not destroyed b/c of bug 12114.

My belief is that the DOM click event is not being destroyed, or is not
releasing its reference to the XUL element, which in turn holds a reference to
the datasource (indirectly via the composite datasource). This has shades of
bug 8836 (actually, it probably _is_ 8836, which was never properly fixed).

Comment 1

[Chris Waterson]

Attachment: test case (save as leak.xul)

Comment 2

[Chris Waterson]

Okay, wait. I was wrong. It seems that clicking the titledbutton works just
fine. To actually force the leak, you need to click OUTSIDE the area of the
tree widget (e.g., in viewer, there is "grey space" beneath the tree control).

Comment 3

[chris hofmann]

how big is the leak?

Comment 4

[Chris Waterson]

bulldozer to M12

Comment 5

[Chris Waterson]

*** This bug has been marked as a duplicate of 18066 ***

Comment 6

[ckritzer (gone)]

Marking VERIFIED DUPLICATE per waterson's comments.

Comment 7

[leger]

BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.