Bug #87906 | Crash on Query Execution | ||
---|---|---|---|
Submitted: | 29 Sep 2017 1:37 | Modified: | 1 Feb 2018 16:27 |
Reporter: | Matt Mitchell | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 6.3.9 | OS: | MacOS (unknown) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[29 Sep 2017 1:37]
Matt Mitchell
[29 Sep 2017 1:38]
Matt Mitchell
Attempted to find the requested log file, but it does not exist on my MacBook.
[6 Oct 2017 10:22]
Pakorn Chongjariyasathaporn
Me too cant Query at all After Update MacOS Hight Sierra
[6 Oct 2017 21:13]
John Kenny
I am having the same problem, when trying to run a query it just show the progress wheel, and I can't close the Tab...the only way out is to Force Quit
[12 Oct 2017 3:29]
Felicity Hughes
Aside from stability/crash problems, the Results Grid will not display. Can only get results by running 'Explain Plan' and then exporting results. Cumbersome to the point of unusable.
[12 Oct 2017 23:43]
MySQL Verification Team
Which exactly MAC OS version are you using (macOS High Sierra)?. Thanks.
[13 Oct 2017 6:42]
John Kenny
I have the same problem on both MacOS Sierra and MacOS High Sierra.
[13 Oct 2017 10:39]
J. Peter M. Schuler
Confirmed. Happens e.g. on macOS 10.13.1 Beta (17B35a), had this issue on other 10.13 version before. First query runs but shows no result window; second query has endless loop.
[19 Oct 2017 17:03]
Demis Flanagan
I'm having the same experience as J. Peter M. Schuler, after upgrading to macOS High Sierra 10.13 (17A405). When I first run a query it appears to be successful based on the response in the Action Output panel but the results grid is not displayed. When I run the query again MySQL Workbench hangs with the activity indication perpetually spinning on the query's tab. Version 6.3.6 build 511 CE(64-bits) Community
[13 Nov 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".
[13 Nov 2017 9:05]
J. Peter M. Schuler
Added the requested wb.log; @Matt could you reopen the status. I switched to PHPstorm for most dev projects, but it is a hassle to not use Workbench anymore.
[8 Dec 2017 9:49]
J. Peter M. Schuler
Fixed for me in 6.3.10
[8 Dec 2017 13:05]
Matt Mitchell
No need to reopen the ticket...version 6.3.10 has been released, which I have downloaded and installed, and so far no issues. The download is available here: https://dev.mysql.com/downloads/workbench/ Matt Mitchell
[1 Feb 2018 16:27]
MySQL Verification Team
Couldn't repeat with 6.3.10.