MySQL Bugs: #75516: Workbench crashes when doing "Open Value in Viewer" on field in the result grid

Bug #75516	Workbench crashes when doing "Open Value in Viewer" on field in the result grid
Submitted:	15 Jan 2015 15:05	Modified:	15 Oct 2015 18:27
Reporter:	John Ericson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.3.4	OS:	Windows (8.1 64-bits)
Assigned to:		CPU Architecture:	Any

Description:
Workbench always crashes when I try to view the value of a field in the Result grid. First I experienced the problem on version 6.2.3 and then decided to upgrade to the latest version, just to find that the same problem occurs there as well.

It happens both on a column that is of data type String and Blob. I need this feature to work in order to view Blob data. A workaround would be appreciated.

The problem happens every time and also on different databases.

The error that happens is that the standard Windows error dialog shows up and it reports that "MySQL Workbench has stopped working". When I press "Close program" the program is terminated.

How to repeat:
1) Do a query on a table.
2) In the result grid right click on a field and choose "Open Value in Viewer". 
3) Workbench crashes.

Thank you for the bug report. Please provide the output of SHOW CREATE TABLE table_name_which_presents_the_reported_behavior. Thanks.

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".

I have this same error.

This does not apply to any specific table. Any time you try to view a value (even simple data types), Workbench crashes.

Having this same problem using Workbench 6.3.4.

Open in Viewer

Attachment: BLOB_ON_VIEWER.png (image/png, text), 217.07 KiB.

I couldn't repeat on 6.3.4 version.

Open Value in Editor

Attachment: ScreenShot436.jpg (image/jpeg, text), 15.11 KiB.

Stopped Working

Attachment: ScreenShot437.jpg (image/jpeg, text), 15.64 KiB.

This is what I get every time in MySQL Workbench 6.3.4.0 build 828 on Windows 7 64 bit. The field type and MySQL Version seems to make no difference.

I updated to 6.3.4 (the "Check for Updates" never reported a new GA version, but I guess that's a separate bug).

I attached to the MySQL Workbench process from VS2013 and got the following exception when trying to open a BLOB:

System.AccessViolationException was unhandled
Message: An unhandled exception of type 'System.AccessViolationException' occurred in mforms.wr.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

My system's memory is definitely not faulty (ran Dell Diagnostics just to be sure).

Exception

Attachment: viewer_crash.png (image/png, text), 128.46 KiB.

Thank you for the feedback. Now I was able to repeat.

Bug #76842 is a duplicate of this one

Did anyone find a way to clean install that "stops reproducing" this bug ? I can't use this tool properly so for me the severity is actually S1.

I have the same problem running 6.3.4.0 Build 828 64 bit on Windows 7 Pro SP1.

Any update?

Thanks...

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

Opening Open Value in Viewer to view the contents of BLOB and string
types would sometimes crash MySQL Workbench.

Thank you for the bug report.