| Bug #11381 | MyODBC leaks | ||
|---|---|---|---|
| Submitted: | 16 Jun 2005 13:13 | Modified: | 3 Sep 2007 14:21 |
| Reporter: | Andrey Hristov | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 3.51.11 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[25 Oct 2005 15:32]
Peter Harvey
Please try c/odbc v3.51.12 and report findings. Any memory issues found in this version will be addressed as reported. Thanks!
[26 Nov 2005 0:00]
Bugs System
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".
[3 Sep 2007 14:21]
Tonci Grgin
This is a duplicate of Bug#15291

Description: I am trying MyODBC by using PHP's ODBC extension and when the scirptie has finished libmysql reports a leak of 16 bytes. ---------------------------------------------------------- Warning: Not freed memory segments: 1 Warning: Memory that was not free'ed (16 bytes): 16 bytes at 0x00827fca0, allocated at line 175 in 'my_error.c' Maximum memory usage: 42997 bytes (42k) How to repeat: PHP CLI (5.1.0-dev here) compiled with ODBC (in the case unixODBC) php -r '$c=odbc_connect("myodbc", "root", "");'