From: Joachim L. <lu...@ho...> - 2001-02-21 18:11:10
|
I did a search about memory leaks in IE in Microsoft's knowledgebase. These are the issues that seemed relevant or could shed a light on this dark matter :-) Complex DHTML Pages Cause Memory Usage to Increase Beyond Bounds http://support.microsoft.com/support/kb/articles/q248/6/30.asp Status: Fixed in 5.01 Memory Leak in Internet Explorer When Background Image Is Resized http://support.microsoft.com/support/kb/articles/q254/6/37.asp Status: Not relevant to DynAPI, but fixed in 5.01 SP1 Memory Leak in Internet Explorer Default Download Behavior http://support.microsoft.com/support/kb/articles/q259/3/65.asp Status: Not relevant to DynAPI, but fixed in 5.5 SP1 Memory Leak in JScript Array.toString and Array.toLocaleString Methods http://support.microsoft.com/support/kb/articles/q281/1/48.asp Workaround: Use Array.join(",") instead of the Array.toString method. Status: Bug exists in JScript 5.5, not in earlier versions COM Objects Created in JScript Not Released Immediately http://support.microsoft.com/support/kb/articles/q164/4/94.asp Status: Not a bug, and not relevant to DynAPI The Array.toString method was the only "live" bug I found, but I don't know if it's used anywhere in the code, but there is a workaround. There must be other issues because I use the workaround in my own code, and I still have the memory problem. Personally I'm suspecting the first one hasn't _really_ been fixed. /Lunna |