A summary of the research on IE memory leak and can't recycle

A summary of the research of IE memory leak and can't recycle one, memory leaks
Before I did see a lot of information, but the eldest brother's words can be a finishing touch, not flatter him, and suddenly opened the two veins of my governor, please see:
Trarck wrote
The reason of memory leakage under IE is circular reference, ie garbage collector can't handle this kind of reference well.
A leaked circular reference is generated, with only isolated DOM objects (out of the DOM tree).
A circular reference between orphaned DOM objects, an orphaned DOM object and a circular reference to a JS object.
Why is it an isolated DOM object? When you leave the page (refresh, jump) deletes the entire DOM tree, the object on the DOM tree is deleted, even if there is a circular reference, it is interrupted at this time.
The isolated DOM objects are: one, created with JS but not added to the DOM tree. Second, removed from the DOM tree.
So avoid leaks, and try not to allow such DOM objects to be generated.
Sometimes such objects are unavoidable, so do not let such an image produce circular references.
The most common circular reference is generated by closures, and the variables (including parameters) in the execution environment reference the DOM object.
After reading this passage, I will only fear to imitate the example of my immediate self-created a new example.
Example 1:

2. <input type="button" value= "Leak" id= "Leak" onclick= "location.reload ();" />
6. <script type="Text/javascript" ><!--
8. (function () {
10. var test=$ (' <div/> ') [0];
12. Test.onclick=function () {};
14. var s=[];
16. For (var i=0;i<10000;i++) {
18. S.push (' aaaa ');
20. }
22. Test.expan=s.join (");
24. //$ (' body '). Append (test);
26. ///Isolated DOM elements will leak
28. })();
30. --></script>

Special case: IFRAME
The Test tool is: sIEve-0.0.8
Refreshes the page in the IFRAME, with a lot of leaks in the page, one more time per brush, but all the leaks disappear when the parent page is refreshed last.
And the IFRAME is proposed to test (refresh) alone, no leakage.

Second, memory recovery
1. Clear global references. The reason is simple, as long as the global reference exists in the browser cannot release the corresponding object, because in the life cycle of the reference, the object may be called at any time.

2. <input type="button" value="to GC" onclick="togc ()" />
4. <script type="Text/javascript"><!--
6. function togc () {
8. g.s=null;
10. }
14. var g={};
16. G.s=[];
18. for (Var i=0;i<100;i++) {
20. G.s.push ($ ('<div /> ') [0]);
22. }
24. --></script>

If you do not click the To GC button, the created Div will never be released until the page unload.
2, each browser different memory release mechanism
A normal (leak-free) page, when it unload (for example, href points to About:blank), the memory release is not the same in different browsers. Did a test, use a famous e-commerce website as the test object.
IE7: There will be no significant release, even if 1 hours, the memory is still high, the minimized window will be released to a few m level.
FireFox3: Not released at any time, no method has been found (except, of course, close the window).
Chrome6: Release now.

A summary of the research on IE memory leak and can't recycle