IE10 DOM-JavaScript circular reference retention diagnosis
0 reputation · 12 Oct 2022, 08:35 UTC
IE10 Trident engine uses a COM-based implementation with a generational garbage collector. Documented behavior indicates DOM-JavaScript circular references can be retained longer than in modern browsers, particularly when attachEvent is used and closures capture DOM nodes.
The supported feature set includes HTML5 video/audio, WebSockets, File API, CSS3 media queries and viewport meta, with document mode selection controlled by X-UA-Compatible meta tag, HTTP header and intranet compatibility settings. Memory management is tied to COM reference counting and the chosen document mode. An unresolved decision concerns memory release for objects created via ActiveX or plugin bridges, where guidance on explicit release is inconsistent and cleanup expectations are ambiguous.
What conditions in IE10 cause DOM-JavaScript circular references to be retained beyond normal collection? Is explicit release required for objects created via ActiveX or plugin bridges, and under what circumstances? How does document mode selection affect garbage collection behavior for DOM-JavaScript references?
ie10