Bug #92589 | MySQL Workbench freeze and sudden shutdown | ||
---|---|---|---|
Submitted: | 27 Sep 2018 19:07 | Modified: | 30 Jun 2019 17:03 |
Reporter: | Paul Passarelli | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S7 (Test Cases) |
Version: | 8.0.12 | OS: | Windows (Microsoft Windows 10 Pro) |
Assigned to: | CPU Architecture: | x86 (HP xw8600 Workstation Xeon) | |
Tags: | WBBugReporter |
[27 Sep 2018 19:07]
Paul Passarelli
[12 Apr 2019 23:12]
MySQL Verification Team
Thank you for the bug report. Could you please try version 8.0.15. Thanks.
[13 May 2019 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".
[13 May 2019 13:18]
Paul Passarelli
I don't have time to go back and reinstall tools to revisit a task more than 6 months old. I provided the steps necessary to recreate the problem. If someone else has the new version described under test and cannot recreate the problem then the issue was fixed. All I can think is that after *decades* of brittleness there is something deep in long forgotten code that is 'brittle' enough to cause a severe crash! I don't know if it's in the parser, grammar, interpreter, lexer, etc. Definition: 'Insanity' -- repeating an identical process over and over hoping for different results. Regards,
[30 Jun 2019 17:03]
MySQL Verification Team
I can confirm that this issue is no longer reproducible with the provided test case and steps using MySQL Workbench Community (GPL) for Windows version 8.0.16 CE build 14498383 (64 bit) on Microsoft Windows 10 Pro. If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL.