Memory Leak When Using "Keep Alive" Connection and SSL Tunneling (216908)



The information in this article applies to:

  • Microsoft Internet Explorer 4.01 for Windows 95 SP 1
  • Microsoft Internet Explorer 4.01 for Windows NT 4.0 SP 1

This article was previously published under Q216908

SYMPTOMS

Users and administrators running Internet Explorer may notice a memory leak when connecting to a Web server using a "keep alive" connection.

CAUSE

The memory leak occurs when Wininet.dll tries to select a "keep-alive" connection from the available pool. If there are none available and the maximum number of connections has already been made to the server, one of the current connections is destroyed. If a Secure Socket Layer (SSL) connection gets destroyed, the secure socket object is often destroyed without cleanly disconnecting the socket connection, resulting in a leak of the security context associated with the secure socket object.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to computers experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix.

To obtain this feature immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
The English version of this fix should have the following file attributes or later:
   Date      Time      Size      File name     Platform
   ------------------------------------------------------
   9/23/98   09:51AM   370,960   Wininet.dll   Windows 95
   9/23/98   10:50AM   370,448   Wininet.dll   Windows NT
				
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/22/2005
Keywords:kbHotfixServer kbQFE kbenv kbprb KB216908