BUG: OLE DataText Prop Doesn't Free Memory When Object ClosedLast reviewed: June 21, 1995Article ID: Q97136 |
The information in this article applies to:
- The Professional Edition of Microsoft Visual Basic for Windows, version 2.0
SYMPTOMSAn OLE destination (OLE client) control (OLECLIEN.VBX) can send data to the OLE source (OLE server) application by setting the DataText property, however the memory allocated for this data is not released until OLECLIEN.VBX is unloaded. The memory is freed when you exit from the application.
STATUSMicrosoft has confirmed this to be a bug in the Professional Edition of Microsoft Visual Basic version 2.0 for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONEach time an OLE destination object is created and the DataText property is set, a new private segment is allocated by OLECLIEN.VBX. When working in the VB.EXE interpreter environment, this segment is deallocated when you exit from VB.EXE or when you start a new project (ALT+F+N). A Visual Basic EXE program deallocates this segment when it is unloaded. The following code uses Microsoft Graph as the OLE source application, but the memory leak also occurs if OLECLIEN.VBX is used with other OLE source programs. To verify that the memory leak occurs, run the code listed below. Then load a tool like Heap Walker that ships with the Microsoft Windows Software Development Kit (SDK), and watch the number of private segments allocated to OLECLIENT change even after the code deletes the OLE objects.
Steps to Reproduce Problem
|
Additional reference words: buglist2.00 2.00 MemLeak
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |