Bug #86430 Possible Memory Leak in Workbench 6.3.9 CE export Data to file function
Submitted: 23 May 2017 13:00 Modified: 25 May 2017 0:06
Reporter: Manuel Dresselhaus Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:6.3.9, 6.3.10 OS:Microsoft Windows (10 64 bit)
Assigned to: CPU Architecture:Any
Tags: crash, memory leak

[23 May 2017 13:00] Manuel Dresselhaus
Description:
I had a Result set of 112740 Lines. Four Rows. Every Row is varchar < 50 characters.

Then I uses the Export function. It doesn't matter, which filetype I choosed. I used csv, csv with ; and excel spreadsheet. It always ends in collecting all the ram it could get until Windows crashes...

I have a new system with Intel i7 7th gen and 16gb ram. No other App was in use. 

Although, a bit strange is, that I was able to export even bigger resultsets. But the Ram consumption was high every time. The hole system just did not crash.

There is no error in version 6.2.

I use that version until there is an update. 

Please reselect the severity if using another version is a valid workaround. There is no workaround with the newest version.

How to repeat:
Generate a big resultset (>100000 rows). Use Export, use filetype Excel Spreadsheet. Whatch the ram consumption in task manager or some other tool.
[25 May 2017 0:06] Miguel Solorzano
Thank you for the bug report.
[4 Jun 2017 14:45] Miguel Solorzano
https://bugs.mysql.com/bug.php?id=86579 marked as duplicate of this one.
[5 Jun 2017 15:26] Gregory Aman
I have the same issue. Issue started after updating MySQL Workbench from 6.3.6 to 6.3.9.
[29 Jun 2017 18:22] Miguel Solorzano
https://bugs.mysql.com/bug.php?id=86873 marked as duplicate of this one.
[14 Dec 2017 8:04] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88665 marked as duplicate of this one.
[8 Aug 2018 18:24] Jared Nishida
Just upgraded my PC to Windows 10 with mySQL version 6.3.10. Memory usage explodes while trying to export.
[6 Mar 20:07] Cesar Vega
I'm having the same issue.  I have to consider an alternative product unfortunately.  Large data exports is all I do.
[6 Mar 20:15] Cesar Vega
Update: reverting to 6.2 corrected the issue.