How To Isolate and Identify the Source of Inetinfo or Other Process Memory Leaks (253706)
The information in this article applies to:
- Microsoft Windows DNA
- Microsoft Internet Information Server 4.0
This article was previously published under Q253706 SUMMARY Memory leaks, regardless of where they occur, tend to
manifest the same behavior. As a process continues to run, a decreasing amount
of memory is available over time and eventually the process can run out of
memory to allocate. Internet Information Server (IIS) has no known
memory leaks at this time. There are, however, typically dozens of components
that are used within the Inetinfo process that may have memory leaks. Over
time, these leaks can accrue, potentially causing the entire process to stop
responding. Be aware that on high volume sites, a growth in memory
over the first 24 hours of use is not uncommon. IIS caches much of its data and
the Time To Live (TTL) on the cache is 24 hours. In fact, the IIS file cache is
set to use up to half of available memory by default. IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
Modification Type: | Minor | Last Reviewed: | 4/6/2006 |
---|
Keywords: | kbBug kbDebug kbGrpDSSIE kbhowto KB253706 kbAudDeveloper |
---|
|