Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#10207 closed defect (fixed)

memory leak on IE load code

Reported by: bill Owned by: James Burke
Priority: high Milestone: 1.4
Component: Core Version: 1.4.0b
Keywords: Cc:
Blocked By: Blocking:

Description

The attachEvent() call on IE should have a corresponding detachEvent() call, at least according to the leak detection program.

I changed hostenv_browser.html from:

window.attachEvent("onload", dojo._loadInit);

to do this:

function runThenDetach(){
	dojo._loadInit();
	window.detachEvent("onload", runThenDetach);
}
window.attachEvent("onload", runThenDetach);

Seems to work, and makes the error go away.

I thought you could alternately just do a

window.detachEvent("onload", dojo._loadInit);

inside of dojo._loadInit, but that's called in multiple ways, like from onreadystatechange.

Change History (3)

comment:1 Changed 10 years ago by bill

Owner: changed from anonymous to James Burke
Summary: memory leak on IE load codmemory leak on IE load code

comment:2 Changed 10 years ago by James Burke

Resolution: fixed
Status: newclosed

(In [20655]) Fixes #10207, help IE help itself.

comment:3 Changed 10 years ago by bill

Milestone: tbd1.4
Note: See TracTickets for help on using tickets.