Bug #187 mysqlimport memory leak
| Submitted: | 24 Mar 2003 7:28 | Modified: | 25 Mar 2003 7:25 |
|---|---|---|---|
| Reporter: | Lenz Grimmer | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
| Version: | 4.0.9 | OS: | Linux (Linux) |
| Assigned to: | Jani Tolonen | CPU Architecture: | Any |
[24 Mar 2003 7:28]
Lenz Grimmer
[25 Mar 2003 7:25]
Lenz Grimmer
Thank you for taking the time to report a problem. Unfortunately you are not using a current version of the product your reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/ If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of MySQL. Running mysqlimport under Valgrind did not reveal any memory leakage. In fact, mysqlimport does not allocate much memory anyway. Most likely, the Linux kernel allocated this memory for buffer cache and will release it, if required.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.