219881 - memory leaked when changing ref attribute of a xul element

Status: RESOLVED EXPIRED

(Core :: XUL, defect)

Description

[Gavin Doughtie]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529

I have a simple XUL app that displays RDF data. With a javascript function
attached to a button in my app, I procedurally set the "ref" attribute of a
template node to different IDs in the RDF file. Clicking back and forth between
two different ref's increases the memory consumed by about 32K each time and it
is never reclaimed. (At least according to the Windows task manager).

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Olivier Cahagne]

can you attach the testcase via "create a new attachment" ?

Comment 2

[Gavin Doughtie]

Attachment: XUL file

simple tree view used by workflows.js

Comment 3

[Gavin Doughtie]

Attachment: Javascript file to illustrate bug

Click the "change ref" button repeatedly to see memory leaked

Comment 4

[Gavin Doughtie]

Attachment: sample data file for illustrating bug

You'll need to edit workflows.js to point to a file URL that points to this
file for the 'change ref' button to work.

Comment 5

[Boris Zbarsky [:bzbarsky]]

If someone could run the leak test on this testcase and find out what objects
are leaking, that would be wonderful....

Comment 6

[Chase Tingley]

I'll run them.  

Possible dup (depends on what's actually leaking): bug 229257

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.