MySQL Bugs: #15366: Handle Leak

Bug #15366	Handle Leak
Submitted:	30 Nov 2005 20:11	Modified:	3 Sep 2007 14:56
Reporter:	Sang Kim	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S5 (Performance)
Version:	3.51.12	OS:	Windows (Windows 2000)
Assigned to:		CPU Architecture:	Any

Description:
Our company develops a software monitoring events called EventSentry.  EventSentry v2.70 has performance monitoring features writing performance data to databases using ODBC. 

When EventSentry writes to a MySQL database through an ODBC connection then our agent leaks handles. After various tests we have determined this leak to be connected to the MySQL ODBC drivers, since the leak does not occur with other databases (e.g. MSSQL).

It seems as if in this case the MySQL ODBC driver is starting a thread and is not closing the thread handle, since performance monitor indicates a thread starting (and ending) every time the handle count increases.

The handle count keeps increasing as EventSentry cointinues to write  to the MySQL database.

How to repeat:
Currently you can only see this with our software EventSentry v2.70 which has not been released to the public yet.

Suggested fix:
Check the code and make sure that handles to all new started threads are properly closed.

We would be happy to do additional testing.

Could you please provide any test case on C. We need to have any case test to find leak of memory on C.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

This is a duplicate of Bug#21385. It may also be related to Bug#14283.