| Bug #86731 | Workbench / Windows Blue Screen of Death | ||
|---|---|---|---|
| Submitted: | 16 Jun 2017 19:58 | Modified: | 17 Jul 2017 0:44 |
| Reporter: | Robert Carver | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S1 (Critical) |
| Version: | 6.3.9 | OS: | Windows (Version 10.0 Build 15063 ) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | Blue Screen Windows Crash | ||
[17 Jun 2017 0:44]
MySQL Verification Team
Thank you for the bug report. Looks like duplicate of https://bugs.mysql.com/bug.php?id=86606.
[17 Jul 2017 1:00]
Bugs System
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".
Description: Without fail, any interaction whatsoever with the results grid immediately causes a fatal Windowsw crash ("blue screen of death"). Appears to have begun after latest you-do-not-get-to-schedule update from Microsoft. How to repeat: Using the results grid, scroll, resize a column, sort a column, edit a resultset column, whatever... Bang! Suggested fix: In order to avoid the suddent crashes I've had to traon myself to never, never touch the results grid. I can export data to Excel for viewing, and iof I want to make a trivial column value change I must use SQL statements.