Bug #17177 Enormous consuming of virtual memory executing LOCAL INFILE
Submitted: 7 Feb 2006 5:57 Modified: 17 Jun 2013 7:41
Reporter: ALex Lysenko Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:3.51.11.00 OS:Microsoft Windows (WIN2K SP4)
Assigned to: Bogdan Degtyariov CPU Architecture:Any

[7 Feb 2006 5:57] ALex Lysenko
Description:
An application writes a table with the very big number of records per second (about 100) using periodical "INSERT LOCAL INFILE". If working via MyODBC 3.51 it takes off all client's system virtual memory in few days and hangs up the system.
(Virtual memory consuming is increasing with each "INFILE")
This bug is absent if the same application works direct via libmysql.dll. 

How to repeat:
execute "INSERT LOCAL INFILE"
into table
   { for example into test table c1 c2 c3 c4 c5 - int}

from static file generated once
   { for example 10 000 rows of five integers  }
frequently
   { for example 2 times per second}

in my case such test causes increasing of VM size about 1 MB / minute 

Remark.
First I did it with file random generated  for each query, then with static file generated once before executing programm.
[7 Feb 2006 6:09] Jorge del Conde
Thanks for your bug report.  I reproduced this using MS Access and 3.51.12 under XP/SP2
[5 Sep 2007 14:48] Miguel Solorzano
Could you please try with latest released version 3.51.19. Thanks in advance.
[5 Oct 2007 23: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".
[29 May 2013 6:19] Bogdan Degtyariov
needs re-verification
[17 Jun 2013 7:36] Bogdan Degtyariov
C test case

Attachment: bug17177.c (text/plain), 2.27 KiB.

[17 Jun 2013 7:36] Bogdan Degtyariov
Sample data

Attachment: data17177.csv (application/octet-stream, text), 23.95 KiB.

[17 Jun 2013 7:41] Bogdan Degtyariov
After 20K iterations each loading file with 500 rows (10M rows in total) I had not noticed any memory increase at all.
Tested with MySQL Connector/ODBC 5.2.5.
Closing the bug.