A memory leak occurs in the Svchost.exe process that hosts a TAPI in Windows 2000 (829697)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Advanced Server
SYMPTOMSIf you have an application that uses the Microsoft Telephony API
(TAPI) to provide Telephony services and the application repeatedly calls the LineInitialize() function and the LineShutdown() function to load the TAPI service provider, a memory leak may occur in the Svchost.exe process that is hosting
the TAPI.CAUSEThis problem occurs because the TAPI relies on remote procedure calls (RPCs) to talk to the TAPI service provider. RPCs use thread local
storage that cannot be deallocated unless a thread-detach call occurs.WORKAROUNDTo work around this problem, make the application call the LineInitialize() function and leave the line
in this state when you develop an application that uses
the TAPI services extensively. Your application can then use the TAPI services, and the memory leak will not occur when the TAPI service providers are unloaded.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Major | Last Reviewed: | 5/4/2004 |
|---|
| Keywords: | kbBug KB829697 kbAudDeveloper |
|---|
|