Article ID: 929874 - Last Review: April 14, 2008 - Revision: 2.1 A memory leak occurs in Internet Explorer 6 when you view a Web page that uses JScript scripting on a Windows XP-based computerOn This PageSYMPTOMSWhen you use Microsoft Internet Explorer 6 on a Microsoft Windows XP-based computer to view a Web page that uses JScript scripting code, a memory leak occurs in Internet Explorer. When you visit a different Web page, the leaked memory is not released.
CAUSEThis problem occurs if circular references are created in the JScript scripting code that is run on the Web page. Or, this problem may occur if closures are used in the JScript scripting code that is run on the Web page. RESOLUTIONSecurity update informationTo resolve this problem, install the most current cumulative security update for Internet Explorer. To install the most current updates, visit the following Microsoft Web site:http://windowsupdate.microsoft.com
(http://windowsupdate.microsoft.com)
For more technical information about the most current cumulative security update for Internet Explorer, visit the following Microsoft Web site: http://www.microsoft.com/technet/security/current.aspx
(http://www.microsoft.com/technet/security/current.aspx)
Note This fix was first included in security update 947864 (MS08-024).
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
947864
(http://support.microsoft.com/kb/947864/
)
MS08-024: Cumulative Security Update for Internet Explorer
REFERENCES
For more information about memory leaks that occur when you visit a Web page, click the following article number to view the article in the Microsoft Knowledge Base:
830555
(http://support.microsoft.com/kb/830555/
)
Circular references to DOM objects on an HTML page cause a memory leak
For more information about Internet Explorer memory leak patterns, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/Bb250448.aspx
(http://msdn2.microsoft.com/en-us/library/Bb250448.aspx)
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. APPLIES TO
| Article Translations
|
Back to the top
