MySQL Bugs: #89866: MySQL Workbench 64 Bit: crash while query on huge table and PC restart required

Bug #89866	MySQL Workbench 64 Bit: crash while query on huge table and PC restart required
Submitted:	1 Mar 2018 11:04	Modified:	9 Jul 2019 14:53
Reporter:	Patrik Schwieger	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3.10.0	OS:	Windows
Assigned to:		CPU Architecture:	x86 (64 bit)

Description:
I have a table which is realy huge due to a BLOB column, each row will be about 5 MB.
Overall entries are about 1200 only, but a query on it with Workbench build in LIMIT 1000 produces following error:

With 32 bit MySQL Workbench I get the error message "client ran out of memory"
That's ok and and I can still work with Workbench and start a new query by setting a lower LIMIT 50 to get some result.

But with 64 bit MySQL Workbench (6.3.10.0) the Workbench crashed and finally the hole PC ned to be restarted, because some Workbench configuration files seems to be locked / corrupted?

How to repeat:
Query a table which is realy huge
SELECT * from tablename LIMIT 1000;

The query starts, the Taskmanager shows that my 3 GB RAM are fully consumed by the process.
Some time later a error message pops up with:
MySQLWorkbench.exe - EXCEPTION
Breakpoint A breakpoint has been reached.

The event viewer shows no error, but this information in System:
Event ID 26: Application popup: MySQLWorkbench.exe - EXCEPTION : Breakpoint A breakpoint has been reached.

--> No MySQL Workbench proccess anymore in task manager

Start the MySQL Workbench again and the journey is going worse.
A Message box pops up:
Home Screen Error
Error while setting up home screen. The errror messega is:
Could not save XML data to file
C:\Users\.....\AppData\Roaming\MySQL\Workbench\connections.xml

Event Viewer in Application
first Event ID 1026 as error from .NET Runtime
Application: MySQLWorkbench.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at <Module>.wb.WBContextUI.finalize(wb.WBContextUI*)
   at MySQL.Workbench.WbContext.finalize()
   at MySQL.GUI.Workbench.Program.Main(System.String[])

second Event ID 1000 as error from Application Error
Faulting application name: MySQLWorkbench.exe, version: 6.3.10.0, time stamp: 0x5a04824f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24024, time stamp: 0x5a58e5b7
Exception code: 0xe06d7363
Fault offset: 0x000000000001a06d
Faulting process id: 0x1574
Faulting application start time: 0x01d3b1446a87ea5a
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 6.3 CE\MySQLWorkbench.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 56ade70a-1d38-11e8-87ee-005056853f96

Trying to connect to my database, Workbench assert the db is not reachable, seems to be down
--> MySQL Workbench can not be used anymore

Finaly after a PC reboot the MySQL Workbench works again and can connect to my db.

The game starts again, if I query the large table......

Suggested fix:
1. avoid a crash while query
e.g. limit the process memory usage in 64 bit builds

2. If the Workbench crashed, avoid the follow up error as seen

Clarification about how to repeat:
Query a table which is realy huge. "huge" means here in terms of one row is huge due to the blob and not the count of table rows at all.

Thank you for the bug report, duplicate/related to bug https://bugs.mysql.com/bug.php?id=83992.

Which part of my report is a duplicate to SSH related stuff?
I do *not* use SSH connection.

Part 1 is about the unlimited memory consumption and a crash
Part 2 is about a crash after the crash due to a possible lock on a file

The affected table has in file system about 7,6 GB and DB internally it’s 5,06 GB with currently 1097 rows as shown with show table status from myDbSchema;
The guilty column in that table is of type mediumblob.

Please re-check based on my last comment if this is really a duplicate

Hello Patrik,

Thank you for the bug report.
Verified this behavior on MySQL Workbench in 6.3.10 version.

Thanks,
Chiranjeevi.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.18 release, and here's the changelog entry:

On Windows, a query made on a table with exceptionally large column data,
such as a BLOB column exceeding 5 MB, caused MySQL Workbench to stop
working (client ran out of memory). On restart of the program, a locked
file prevented additional queries until the computer was restarted.

Thank you for the bug report.