Jon Sykes blogged about a memory leak he happened upon that, potentially, can have huge consequences memory wise when dealing with the FORM DOM element. Jon outlines the problem and why it is a problem to developers.
What is the leak?
Apparently if you try to remove/destroy/trash a FORM dom node in IE6, it won’t delete it, instead creating a bizarre orphaned node stuck sucking up memory until the browser window is refreshed.
Why is this an issue?
If you have a “web application” that uses any form of partial page loading, and the content you are loading contains any form elements, in IE6 memory usage will climb as you use the app, leading to initially a sluggish browser and finally total terminal failure.
As many of the toolkits these days come with this style of content loading mechanism (take for example my toolkit of choice dojo, with it’s contentPanes), it’s very easy to get into a situation where your webapp will be unacceptable to folks using IE
Popularity: 4% [?]
Recent Comments