Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: Memory Leak When You Use a GETENV Call in DllMain
Article ID: 815315 - View products that this article applies to.
C runtime libraries have data structures to track thread-specific state data. When you use some specific C runtime library functions (such as getenv) in DllMain, the memory might be allocated two times for these thread-specific data structures. This problem can cause a memory leak.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 Service Pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name --------------------------------------------------- 21-Mar-2003 14:50 6.1.9844.0 286,773 Msvcrt.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.