| Bug #26933 | Memory Leak in SQLTables function | ||
|---|---|---|---|
| Submitted: | 7 Mar 2007 20:10 | Modified: | 8 Mar 2007 2:14 |
| Reporter: | Joe Roberts | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 3.51.12 | OS: | Windows (Windows 2000 Server) |
| Assigned to: | CPU Architecture: | Any | |
[8 Mar 2007 2:14]
Jim Winstead
This is a duplicate of Bug #26932.

Description: I profiled our code which calls SQLTables using Rational Purify and it always shows huge memory leaks every time that SQLTables is called - it seems that the problem is always reported with SQLTables and then the Kernel level APIs as the root of the leak. How to repeat: Create a table in database on the server, use the same version of the MyODBC driver and call SQLTables as follows: ret = SQLTables(hstmt, NULL, SQL_NTS, NULL,SQL_NTS, tableName, SQL_NTS, NULL, SQL_NTS); Profile the code with a tool such as Rational Purify to see the memory leak.