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
Maybe we should run mysqlimport under Valgrind to test this? 
Date: Fri, 21 Mar 2003 10:20:40 +0800 
From: philip_ng@ceicdata.com 
To: mysql@lists.mysql.com 
Subject: mysqlimport memory leak 
Linux Redhat 7.3 
MySQL 4.0.9-gamma 
I tried to import a 900M file with mysqlimport command. Everything works fine. 
All the data has been insert into the DB. 
However, all the memory has been used up. Before the mysqlimport, I have 800M 
free memory, after that, 13M free memory left. 
Is there any way to limit the mysqlimport operation size. For example, limit 20M 
for the whole mysqlimport. 

How to repeat:
[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.