Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#1205 closed defect (wontfix)

memory in DomWidget related to event (0.3.1, Firefox 1.5)

Reported by: andy.afei@… Owned by: alex
Priority: high Milestone:
Component: Events Version: 0.3
Keywords: Cc:
Blocked By: Blocking:

Description

Seems there is a memory leak in DomWidget?.js related to event as reported by the leak monitor tool on Firefox 1.5.

To reproduce: load test/widget/test_Button.html and the navigate away from it, get report like:

[+] [leaked object] (37432e8, http://.../dojo/dojo.js, 323-325) = function (evt) {

if (_this[ntf]) {

_this[ntf](dojo.event.browser.fixEvent(evt, this));

}

}

[ ] prototype (11cbc30) = [object Object]

[+] [leaked object] (3056ab8, http://.../dojo/dojo.js, 323-325) = function (evt) {

if (_this[ntf]) {

_this[ntf](dojo.event.browser.fixEvent(evt, this));

}

}

[ ] prototype (11cbc40) = [object Object]

......

More lines like these, probably one for each widget or event connect.

From the source code, it is from DomWidget?.js at line 228 and 254 (version 0.3.1):

return function(evt){ if(_this[ntf]){ _this[ntf](dojo.event.browser.fixEvent(evt, this)); } };

Change History (5)

comment:1 Changed 13 years ago by dylan

Milestone: 0.4

comment:2 Changed 13 years ago by dylan

Priority: normalhigh

comment:3 Changed 13 years ago by dylan

Milestone: 0.40.4.1

an issue in firefox 1.5, appears to not be an issue with firefox 2 RC2.

comment:4 Changed 13 years ago by alex

Resolution: wontfix
Status: newclosed

If the browser is going to fix it, then I don't think this needs "solving". Marking "wontfix"

comment:5 Changed 12 years ago by (none)

Milestone: 0.4.1

Milestone 0.4.1 deleted

Note: See TracTickets for help on using tickets.