Main Page
From Drip IE Leak Detector
| Revision as of 20:16, 22 July 2006 85.107.156.96 (Talk) ← Previous diff |
Revision as of 20:17, 22 July 2006 85.107.156.96 (Talk) Next diff → |
||
| Line 26: | Line 26: | ||
| * [http://blogs.msdn.com/ericlippert/archive/2003/09/17/53028.aspx What are closures?] | * [http://blogs.msdn.com/ericlippert/archive/2003/09/17/53028.aspx What are closures?] | ||
| * [http://www.quirksmode.org/blog/archives/2005/10/how_do_i_create.html QuirksBlog: How do I create a memory leak test script?] | * [http://www.quirksmode.org/blog/archives/2005/10/how_do_i_create.html QuirksBlog: How do I create a memory leak test script?] | ||
| - | * [http://www.codeproject.com/jscript/leakpatterns.asp The Code Project Memory Leakage in Internet Explorer Revisited] | + | * [http://www.codeproject.com/jscript/leakpatterns.asp The Code Project: Memory Leakage in Internet Explorer Revisited] |
Revision as of 20:17, 22 July 2006
Contents |
IE Memory Leaks
OutOfHanwell.com took the initiative to host Drip (a memory leak detector for Internet Explorer) after it was no longer available through Joel Webber's blog and has made some revisions to the tool under its BSD license.
If you wish to contribute or if you have specific thoughts or suggestions regarding the Drip tool, please visit the SourceForge project page.
Download
The latest version (see release notes for version 0.3 and version 0.4) can be downloaded from:
- Drip-0.4.exe: binary executable
- Drip-0.4-src.zip: source code
(Note that OutOfHanwell.com is not affiliated with Joel Webber in any way.)
Drip's Limitations
Although Drip can catch the most common causes of memory leaks in Internet Explorer, there are certain memory leaks that occur outside the realm of the web page.
Specifically, pages with hidden table cells will leak memory when they are unloaded. This leak is not caused by JavaScript code, and it can only be avoided by capturing the "onbeforeunload" event and displaying all hidden table cells. Because only a small amount of memory is leaked, it is possible that certain pages can ignore this leak with no severe consequences.c
