MySQL Bugs: #88665: Run-away memory use when exporting recordset

Bug #88665	Run-away memory use when exporting recordset
Submitted:	27 Nov 2017 14:00	Modified:	14 Dec 2017 8:04
Reporter:	Jon Munslow	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.3.10	OS:	Windows (Microsoft Windows 7 Professional Service Pack 1)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Run away memory use when exporting recordset 
to external file.  Once export eventually completes
the memory is still not realeased.

Certainly affects saving to .csv and .xml  
but I think all file types are equally affected.

How to repeat:
Run a select statement in workbench to generate a recordset.
 
Monitor MySQLWorkbench.exe memory use through windows task manager  

Export recordset. 

Watch task manager as workbench consumes all the memory and doesnt realease it once save is complete

 

Suggested fix:
Find and fix the source of the memory leak...

Update:  Problem persists despite upgrading to 6.3.10

Hello Jon Munslow,

Thank you for the bug report.
This is most likely duplicate of Bug #86430, please see Bug #86430

Thanks,
Chiranjeevi.

Same bug here. The export is very slow. Version: 6.3.10

windows 10