Comments on: Unload event never fires in IE

By: sawan

sawan — Thu, 19 Feb 2009 07:51:34 +0000

this code works good for problem mentioned above , but my problem is to stop unloading of document on the event onbeforeunload.

By: Spocke

Spocke — Tue, 06 May 2008 07:29:06 +0000

The fixUnload doesn’t leak in the example since it’s not used inside a closure. But the stop function is so it needs to be properly detached.

This code is more of a proof of concept than a real usable code piece normally you would contain it in a library and then you need to fix it up a bit.

By: Mathew Robertson

Mathew Robertson — Tue, 06 May 2008 06:23:48 +0000

A question for those smarter than me…

Wouldn’t the “onbeforeunload” cause a leak (aka the JS/DOM style leak), since it is never detached?

ie: shouldn’t the setTimout() also detach the “fixUnload”?

By: Javascript News » Blog Archive » Are you sure your unload handler is firing in IE?

Thu, 17 Apr 2008 20:52:18 +0000

[...] Sörlin found that sometimes his unload event never fired in IE: We recently found a serious bug in IE where the unload event wouldn’t fire on a specific page [...]

By: Spocke

Spocke — Thu, 17 Apr 2008 17:41:56 +0000

This is a bug since the unload event should always fire if a document is unloaded. I don’t see how this has anything to do with DOMReady you tend to want to add events before all contents is loaded on the page DOMReady is normally fired before the onload event and that is the problem.

You must remove the event handles on unload in IE if you use closures or it will leak and the only way to do that is to use the unload or beforeunload events.

By: Nicolas

Nicolas — Thu, 17 Apr 2008 17:10:18 +0000

I hardly see this one as a bug: since the onload event didn’t trigger in your example, I can understand why the unload do not as well.
So, if you use the onload to attach and onunload to detach your events, you’re not leaking.
But if you use a “DOMReady” technique, you’re in trouble if you use the onunload. You should use some kind of “DOMDisposed” technique then.

By: Ajaxian » Are you sure your unload handler is firing in IE?

Ajaxian » Are you sure your unload handler is firing in IE? — Thu, 17 Apr 2008 15:52:31 +0000

[...] Sörlin found that sometimes his unload event never fired in IE: We recently found a serious bug in IE where the unload event wouldn’t fire on a specific page [...]

By: Bram.us » TinyMCE 3.0.7 Released

Bram.us » TinyMCE 3.0.7 Released — Mon, 14 Apr 2008 16:15:28 +0000

[...] table or add classes to it. This was also added to normalize the browser behavior. We also fixed a new type of memory leak in IE” – Announcement – Download – Changelog Spread the [...]

By: Spocke

Spocke — Tue, 08 Apr 2008 22:29:30 +0000

@Bramus: It affects IE6 and IE7 haven’t tested IE8.
@Martin: Yes, it’s a real ugly hack. Yes, trapping F5 might work just fine I will fiddle somewhat with that.

By: Martin

Martin — Tue, 08 Apr 2008 15:21:56 +0000

Okay, it’s really a hack, but it’s internet explorer…

Why do you don’t use a keycode to listen for the F5? Okay, it wouldn’t triggered if you hit the refresh button.

Greetings,
Martin