Bug #89745 Workbench hard crash on pressing "Results grid" on update/insert explain
Submitted: 21 Feb 2018 10:05 Modified: 21 Apr 2020 21:18
Reporter: Lee Butler Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:6.3.9/10 OS:Windows (10)
Assigned to: CPU Architecture:Any
Tags: execution plan, results grid

[21 Feb 2018 10:05] Lee Butler
I have identified a bug which occurs which causes Workbench on Windows to hard crash (App close and WERFault appears) which I have managed to replicate.

For easy replication, you can create a table (test) with a column (testcol), then EXPLAIN "INSERT INTO test (testcol) VALUES ('apples');" for example. 

I feel like increasing the severity, but I'm not sure. I wasn't expecting the query to execute when I clicked Results Grid, and as I was working in a production environment, I could have inadvertently done something bad. As it happens, I wanted to run the query anyway, but still. 

How to repeat:
1. Write a statement which does not generate a result set, like an INSERT or UPDATE statement. 

2. Click the "Execute EXPLAIN statement" button (5th from left)

3. On the right sidebar in the lower pane, click "Result Grid"

4. Workbench will execute the statement that you wrote, without the explain, and then crash.

5. When you reopen workbench, select the table you updated/inserted and see that the request you made ran anyway prior to crashing.

Bonus bug/issue: 
When on the Explain grid, the "Tabular Explain" dropdown also has the visual explain option. However, selecting this does nothing and it reverts to Tabular anyway.
[21 Feb 2018 10:28] MySQL Verification Team
Hello Lee Butler,

Thank you for the report and steps.
Observed this on Win7 with MySQL Workbench Commercial (Proprietary) for Windows version 6.3.10 SE build 12092614 (64 bit).

[21 Apr 2020 21:18] Christine Cole
Fixed as of the upcoming MySQL Workbench 8.0.21 release, and here's the proposed changelog entry from the documentation team:

On Windows, statements that do not generate a result set, such as INSERT
or UPDATE statements, caused MySQL Workbench to close unexpectedly after
the EXPLAIN operation was executed and then the Result Grid output type
was selected.

Thank you for the bug report.