Comments on: stickyWinHTML layout update: big close/ok buttons

by: Aaron N.

Thu, 05 Apr 2007 17:15:05 +0000

IE, for some odd reason, eats memory when you create a big block element (in this case, the modal layer). If I were a betting man, I’d bet that it creates a bitmap or something that it renders the whole page with. The bigger the element, the more bits, the more bytes, etc.

Modalizer re-uses the same modal layer over and over again, so if you create 10 of them, they all point to a single DOM element. I do this precisely because of how IE eats memory for each one. If you have altered Modalizer so that it will create numerous layers, you’ll see it eat memory for each one.

Yay MSFT.

by: JimK

Thu, 05 Apr 2007 16:33:40 +0000

Yeah when I refresh the page in between popups, it’s fine. It’s when I don’t refresh the page and just keep opening and closing the same stickyWinModal… or when I have links that will pop up a number of stickyWinModals on one page and go from one to the next without refreshing the page. That’s when I see the stair step. The more content in the window, the more pronounced the step… is there something I’m not doing correctly to release the modal when I close it?

I don’t have a page I can point you to at the moment… I’ll try to get an example later tonight.

by: Aaron N.

Wed, 04 Apr 2007 19:12:50 +0000

I can’t reproduce this Jim. Here’s the memory chart of me creating a StickyWinModal and refreshing the page and doing it again in IE7 (using the example in the wikitorial):

Can you point me at the page where this is happening to you?

by: JimK

Tue, 03 Apr 2007 16:05:00 +0000

Ok, I think I figured out my problem. Regarding the onClose not working, it appears that I had a version out of sync, possibly the stickyWin.js, but I’m not sure. I grabbed fresh copies of everything and that seems to have cleared it up. I’m now using mootools.net rev 430 with your svn trunk for the clientside. The hanging of IE7 seems to have been because in the onClose, I was trying to clear the stickyWin myself (to kill a sound that continues to play after the stickyWin is closed) and apparently it really didn’t like that… my bad #2.

Here’s a problem I’m still having though. It appears the stickyWinModal leaks memory in IE7. If I just create a simple modal with no crazy functionality and keep opening and closing it, I get the stair step action like you mention in your article on “Screencast on Diagnosing Memory Leaks in IE.”

BTW, you’re doing a hell of a job here. Your widgets and your articles have been invaluable in my efforts and are greatly appreciated. Keep up the good work, please.

Thanks

by: Aaron N.

Mon, 02 Apr 2007 17:36:04 +0000

Hmmm. I’d need to see it in action. Which release of the SVN are you using? Have you tried your code with the version in our SVN release? This might tell us if it’s a change in Mootools that is the problem, a problem with my code, or a problem with yours. If you can give me these answers and point me at an example, I might be able to help.

by: JimK

Mon, 02 Apr 2007 16:18:00 +0000

Any chance you can give me some hints on why the onClose in StickyWin wouldn’t be working with Mootools after 1.0, specifically the latest SVN? My stickyWin hangs IE 7.. basically if I have a bunch of links and events going on in the popup, I can get IE7 to hang after a bit. This doesn’t happen with the latest mootools, but I really need the onClose functionality. Any pointers or tips would be greatly appreciated.

Thanks

by: JimK

Mon, 26 Mar 2007 16:43:54 +0000

I was using the dev version from Mootools.net. Actually the official 1.0 released version I was having some problems with the ajax callback not getting called. Switching to dev cured that. I just tried the clientside.moo.v1.packed.js file and both ajax and the stickyWin onClose function are working, although the onClose is getting called twice. Still, that’s much better. Thanks

by: Aaron N.

Sat, 24 Mar 2007 00:43:58 +0000

Are you using the copy of Mootools in my SVN, or one from Mootools.net? If from Mootools.net, are you using the dev version or the current “public” version?

Try downloading from my SVN the clientside.moo.v1.packed.js file (in trunk/cat/) and seeing if it works on your page with that.

by: JimK

Sat, 24 Mar 2007 00:39:20 +0000

That’s what I thought. I’m not using the stickyWinHTML or the buttons, just a stickyWin and using the closeSticky classed anchor to close the stickyWin. Even when I strip it down to a simple test, like below, it never pops up my alert… neither display nor close. Some version incompatibality maybe?

var x = new StickyWin({
content: $(’stickyWinContent’).innerHTML,
onDisplay: function(){alert(’display’);},
onClose: function(){alert(’close sticky’)}
});

by: Aaron N.

Fri, 23 Mar 2007 22:56:19 +0000

Corrected code example above; had onDisplay in there twice