Reopen Workbench and the session should now be working. Here after a few seconds Workbench will give you an error that it can't autosave (path not found). Rm -rf tosave OR rm -rf SERVER1-3.workspace Where the number after the "-" is the tab position, if you are having trouble with the third session tab it would be Rm -rf tosave OR rm -rf SERVER1-1.workspace Users/foo/Library/Application Support/MySQL/Workbench/sql_workspacesĪnd deleted the sessions directory which will have one of two names depending on the state it is (most probably. With Workbench OPEN (IMPORTANT, it wont work if workbench is closed) I deleted both files from the problematic connection. column_widths file for each of your connections. Users/foo/Library/Application Support/MySQL/Workbench/cache And if any of your open sessions is in this unstable state then Workbench will not close.īased on this and Chris Botman's comment I went to:
It seems to depend on the session and the order it is opened, for example if you have session SERVER1 and it is not working, when you open a second SERVER1 session it will work until someday it crashes (note that it doesn't have the same saved tabs because it is a different session even if the connection is the same). I noticed that whenever a session hangs that session will start having persistent issues running queries. I might be speaking too soon but it has been working for me so far: Gabriel Capparelli It´s incredible that this issue still persists but I think I found a workaround based on Chris Botman's comment. I am using MySQL Workbench 6.3.7, and am connecting to databases running 5.7.11-log. At the moment, I can execute some simple queries, but any time I attempt to query a large table (even with a limit of 1000 records), I am now getting a crash.įor me, I think there's a decent chance that this started after I upgraded to macOS Sierra.
autosave items in the sql_workspaces directory, which removed the "autosaved" state, but didn't fix the issue. I reinstalled the application, to no avail. For a while, I wasn't able to execute any queries on any connections. In addition to very often getting the "Cannot close SQL IDE while being busy" error, if I click the "Reconnect to DBMS" button, it hangs the application, necessitating a force-quit. I believe that, as stated in original post, it is triggered by (or coincidental to) a crash that necessitates force-quitting the application. JC Quirin For what it's worth, this has been happening to me constantly for the past couple of weeks.
0 kommentar(er)
