KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q262173: Memory Leak Occurs When MSWC.IISLog Is Repeatedly Instantiated

Article: Q262173
Product(s): Internet Information Server
Version(s): winnt:5.0
Operating System(s): 
Keyword(s): kbDSupport kbiis500 kbWin2000SP2Fix
Last Modified: 08-MAY-2002

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Internet Information Services version 5.0 
-------------------------------------------------------------------------------

SYMPTOMS
========

A memory leak may occur when the Internet Information Server (IIS) Log component
(IISLog) is repeatedly instantiated. The amount of memory loss that occurs is
directly related to the number of times that the IIS Log Component is
instantiated.


CAUSE
=====

This problem occurs because there are Active Template Library (ATL) macros
calling the SysAllocString function with no corresponding the SysFreeString
function.

STATUS
======

Microsoft has confirmed this to be a problem in Internet Information Services
version 5.0.


Additional query words:

======================================================================
Keywords          : kbDSupport kbiis500 kbWin2000SP2Fix 
Technology        : kbiisSearch kbiis500
Version           : winnt:5.0
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbpending

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.