Bug #86430 Possible Memory Leak in Workbench 6.3.9 CE export Data to file function

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.

Thank you for the bug report.

https://bugs.mysql.com/bug.php?id=86579 marked as duplicate of this one.

I have the same issue. Issue started after updating MySQL Workbench from 6.3.6 to 6.3.9.

https://bugs.mysql.com/bug.php?id=86873 marked as duplicate of this one.

http://bugs.mysql.com/bug.php?id=88665 marked as duplicate of this one.

Just upgraded my PC to Windows 10 with mySQL version 6.3.10. Memory usage explodes while trying to export.

I'm having the same issue.  I have to consider an alternative product unfortunately.  Large data exports is all I do.

Update: reverting to 6.2 corrected the issue.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.21 release, and here's the proposed changelog entry from the documentation team:

Memory use on a Windows host was excessive when a large result set was
exported to a file, causing MySQL Workbench to become unresponsive.

Thank you for the bug report.