Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I realize IE7 is in Beta and could be (is) buggy but I would like to report to you a possible issue so that you can be aware of it. Or maybe I am just dumb and am screwing something up.
var x = document.createElement("DIV");
x = null;
var x = document.getElementById("mydiv");
x = null;
I first strike the button that adds the div, I then strike the button that deletes the div.
When I run drip on a machine with IE6 installed, no reported leaks, when I run on an IE7 install, I recieve a warning that the div element still exists and is leaked
http://localhost/WbG30219_62_MemmoryLeak/Default2.aspx (5 references)
Again, this is probably either programmer error or a browser engine issue.
I have checked in a simplified test case at http://svn.sourceforge.net/viewvc/ieleak/trunk/drip/src/tests/ie7b3-domExpando.html?view=markup.
This is a regression in ie7b3. I have filed a bug report with Microsoft.
By the way, thanks a lot for taking the time to report this issue. It's really helpful to me that you've pointed this out, rather than waiting until IE7 is released.
No problem on the report, when you get the link for the bug from MS, could you post it? My management would like to keep on this issue since our customers will report this to us as something we are doing and we would like to keep them a float on what is going on.
Here it is:
It looks like the code responsible for this issue made it in to the production release of IE7. I also did a simple page very similar to the one citsuac did (a couple of functions hooked to button elements)
TestDiv = document.createElement("div");
TestDiv.style.top = "10px";
TestDiv.style.left = "10px";
TestDiv.id = "TestDiv";
TestDiv.innerHTML = "TestDiv";
TestDiv = null;
TestDiv = document.getElementById("TestDiv");
TestDiv = null;
The output from the Drip tool shows 5 references to TestDiv are being held
http://localhost/home//IIWin/LeakTest1.htm (5 references)
The call to window.CollectGarbage() ran, but it makes no difference either way as to the leaks reported by the tool.
I followed the feedback link https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=175306 for when the issue was originally posted with Microsoft but I'm getting a message page that the site is temporarily closed. Does anyone here know what the status is?
Also, where is the latest version of the tool? It looks like there is no version available for download right now.
I will try to look into this issue when I have a chance.
Microsoft has closed down their IE Connect site for quite a while. I haven't heard any reasons why.
You can find the latest version of Drip at http://www.outofhanwell.com/ieleak/