Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Internet Explorer 6 appears to stop responding, and you may also notice a memory leak on the computer


View products that this article applies to.

Symptoms

When you start Microsoft Internet Explorer 6, you cannot connect to a Web site, and Internet Explorer 6 appears to stop responding (hang). This issue occurs even when you close one or more browser windows when the maximum number of simultaneous connections that the server allows is reached. You may also notice a memory leak on the computer.

↑ Back to the top


Cause

This issue occurs if a Web page contains a script that creates XMLHTTP objects and uses the OnUnload event in JavaScript. The XMLHTTP objects are released but not destroyed during the OnUnload event.

↑ Back to the top


Workaround

To work around this issue, use the JavaScript abort method on the XMLHTTP objects to clean up the XMLHTTP objects when the Web page is unloaded. For example, the following code example uses the abort method on the g_httpObj object.
<BODY onUnload="abortxml()"> 

function abortxml()
{
if (g_httpObj))
  {
      g_httpObj.abort();
  }
}
Note In this code example, g_httpObj is a placeholder for an XMLHTTP object.

↑ Back to the top


More information

When the XMLHTTP objects are not destroyed, the connection handle object to the server may not be released as expected. When the connection handle object is not destroyed, you cannot open a new Internet Explorer 6 window if the maximum number of simultaneous connections that the server allows is reached.

↑ Back to the top


Keywords: KB886710, kbprb

↑ Back to the top

Article Info
Article ID : 886710
Revision : 3
Created on : 7/6/2005
Published on : 7/6/2005
Exists online : False
Views : 291