BUG: Memory Leaks in DirectX Visual Basic DirectPlay Interfaces (319479)

The information in this article applies to:

Microsoft DirectX Software Development Kit 8.1

This article was previously published under Q319479

SYMPTOMS

The following methods in Microsoft DirectPlay IDirectPlay8Peer interface leak between 30 and 50 bytes per call:

GetClientInfo
GetServerInfo
GetPeerInfo

CAUSE

The problem occurs because of a bug in the DirectX Visual Basic (DXVB) layer, which does not free an object that the DXVB layer allocates for the methods that are listed in the "Symptoms" section.

RESOLUTION

Microsoft recommends that you do not use these methods. If you must use these methods, call these methods as rarely as possible, and cache the information for later use to minimize the memory leakage.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Behavior

Use the SimpleServer and the SimpleClient samples that are included with DirectX SDK 8.1.
Connect to at least two users.
Click make face.

If more than one person is logged on, you receive the message <player x> is making faces at you. Note that the memory usage increases gradually and does not decrease until the program quits.

Modification Type:	Minor	Last Reviewed:	2/11/2004
Keywords:	kbDSWNET2003Swept kbAPI kbbug kbDirectPlay kbnetwork kbpending KB319479