FIX: Cursor Library Memory Leak in Multithreaded Environment

Last reviewed: October 29, 1997
Article ID: Q171878

The information in this article applies to:

Microsoft Open Database Connectivity, versions 2.5 and 3.0

BUG #: 1251/4210 (odbcsdk)

SYMPTOMS

When the cursor library is loaded in a multithreaded application, a memory leak occurs.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Open Database Connectivity versions 2.5 and 3.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft Open Database Connectivity, version 3.0. For more information, contact your primary support provider.

MORE INFORMATION

This problem is created when multiple threads establish connections specifying that the ODBC Cursor Library is to be used. For example, if each thread of a multithread application creates a connection using the SQLSetConnection(hdbc, SQL_ODBC_CURSORS, SQL_CUR_USE_ODBC) statement and subsequently executes it repeatedly, you can use the Process Viewer to observe a memory leak.

Additional query words: 6.50 6.5 sql sqlserver server multi thread threaded
Keywords : kbbug2.50 kbbug3.00
Version : 2.5 3.0
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.