Bug #25829 falcon handle leak: if process has been terminated manually
Submitted: 24 Jan 2007 14:55 Modified: 25 Jan 2007 10:39
Reporter: Mikko metsola Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version:mysql-5.2.0-falcon-alpha-win32 OS:Windows (Win XP)
Assigned to: CPU Architecture:Any

[24 Jan 2007 14:55] Mikko metsola
Description:
according to my program: 2 handles are leaked in the following Falcon scenario:

1. sql_init(db);
2. mysql_real_connect(db, ...)
(2.5 make some queries or not)
3. kill the underlying mysqld database server from task manager 
4. mysql_close(db);

There was no leaks in that scenario in 5.1.11 version that I used to use. 

I dont call mysql_shutdown in that particular scenario, because the server process is already down (and I didnt call mysql_shutdown in 5.1.11 either).

rgds, MMe

How to repeat:
Make a small program that uses 5.2.0-falcon C-API (libraries libmysql.lib and libmysql.dll) and chronologically perform the actions in your code.
[25 Jan 2007 10:39] Mikko metsola
You can close this fault. I had one process handle that remained open in my code.