Microsoft KB Archive/319479

= BUG: Memory Leaks in DirectX Visual Basic DirectPlay Interfaces =

Article ID: 319479

Article Last Modified on 2/11/2004

-

APPLIES TO


 * Microsoft DirectX 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 &quot;Symptoms&quot; 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.



Steps to Reproduce the Behavior

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

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

Keywords: kbbug kbapi kbnetwork kbdirectplay kbpending kbdswnet2003swept KB319479

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.