Comments on: Setting Up Elements http://mootools.net/blog/2010/06/10/setting-up-elements/ The Blog Mon, 20 May 2013 09:32:37 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: con http://mootools.net/blog/2010/06/10/setting-up-elements/comment-page-1/#comment-1134 con Mon, 14 Jun 2010 12:33:07 +0000 http://mootools.net/blog/?p=982#comment-1134 <p>Thanks Sean, this looks very useful.</p> Thanks Sean, this looks very useful.

]]> By: Sean McArthur http://mootools.net/blog/2010/06/10/setting-up-elements/comment-page-1/#comment-1132 Sean McArthur Sat, 12 Jun 2010 20:35:34 +0000 http://mootools.net/blog/?p=982#comment-1132 <p>@con: I don't know of much that will help you to find memory leaks other than to leave the browser open for a while and watch if it's memory usages has steadily gained in the Task Manager.</p> <p>The main culprit is, of course, Internet Explorer. The memory leak is explained well <a href="http://www.jibbering.com/faq/notes/closures/#clMem" rel="nofollow">here</a> and <a href="http://www.ibm.com/developerworks/web/library/wa-memleak/" rel="nofollow">here</a>. They touch on the issue IE has with garbage collecting objects with circular references.</p> @con: I don’t know of much that will help you to find memory leaks other than to leave the browser open for a while and watch if it’s memory usages has steadily gained in the Task Manager.

The main culprit is, of course, Internet Explorer. The memory leak is explained well here and here. They touch on the issue IE has with garbage collecting objects with circular references.

]]> By: Timothy http://mootools.net/blog/2010/06/10/setting-up-elements/comment-page-1/#comment-1131 Timothy Sat, 12 Jun 2010 13:37:29 +0000 http://mootools.net/blog/?p=982#comment-1131 <p>Pretty cool. Going to try these out soon.</p> Pretty cool. Going to try these out soon.

]]> By: con http://mootools.net/blog/2010/06/10/setting-up-elements/comment-page-1/#comment-1130 con Sat, 12 Jun 2010 09:44:34 +0000 http://mootools.net/blog/?p=982#comment-1130 <p>Thanks for this great article! I use a lot of direct referencing with elements the way you describe as bad practice: el.prop = { someEl: el } instead of el.store(..) (mostly because of lazyness :) it's quicker to write ;) - Is there a way to find (possible) memory leaks easily? I suggest they also depend on different browsers and how good their garbage collection is working?</p> Thanks for this great article! I use a lot of direct referencing with elements the way you describe as bad practice: el.prop = { someEl: el } instead of el.store(..) (mostly because of lazyness :) it’s quicker to write ;) - Is there a way to find (possible) memory leaks easily? I suggest they also depend on different browsers and how good their garbage collection is working?

]]>