TAPI Server Leaks Memory When Multiple Programs Own Calls (310626)

SYMPTOMS

Memory leaks slowly in Tapisrv.exe when more than one program is working with the same incoming call. For example, call center program architecture may necessitate that multiple processes own a given call. When this occurs, some tracking data that is associated with call handles may not be freed when the last reference to the call is dropped by using lineDeallocateCall. The amount of memory that is leaked by each call is at least 40 bytes, and is directly proportionate to the total number of call owners, where the number of owners is greater than 2.

RESOLUTION

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 hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note 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.

TAPI Server Leaks Memory When Multiple Programs Own Calls (310626)

SYMPTOMS

RESOLUTION

STATUS