It's obvious it crashes when the connection is idled out. When I leave Workbench window for a couple of minutes and then get back - it stops responding on trying to start any SQL operation. Workbench works when I perform SQL operations continuously (breaks between operations shorter than 5 minutes). I have plenty of such events in my event log. The program MySQLWorkbench.exe version 6.3.8.0 stopped interacting with Windows and was closed. Another info that could be helpful tracking down the slowness is enabling verbose logging in WB (start it with -log-level=debug3) and monitor the WB log file (Help -> Locate Log File), to see if it will print what it's doing when the slowness happens.Īdam Łyskawa Windows 10, 圆4, same behavior. Ideally, the server's general log would be monitored to see what's WB doing when it's slow, but that's not always possible. If there's any case that is not covered by these scenarios and can't be explained by just how long it takes for the server to execute a query, please leave a comment explaining. This can only be made as fast as the time it takes to run SHOW DATABASES.Īnother problem was the context sensitive help, which would kick in while typing, but in 6.1 this was fixed to work from a thread and additionally, to only kick in on demand. There's also the population of the schema tree in the sidebar. We can improve this, but to confirm that this is really the problem, you can disable Code Completion in Preferences and see if it helps. One of them may be caused by code completion, which needs to retrieve the list of objects in the current default schema from the server. doesn't seem to matter as we see this type of crashing behavior in all instances and on various flavors of Windows OS (notably Server versions 2008 R R2, and Desktop all varieties of Win 7/8/8.1)Īlfredo Kojima From the comments, it looks like different things cause unresponsiveness. on the server itself, on a desktop on the LAN, or a remote desktop connected to the server via VPN. In each case it seems like the Workbench client is making some form of query to the server (though I don't know what all is cached locally, such as table lists or auto-complete items), but sometimes whatever that process is seems to fail in a way that causes Workbench to crash (occasionally it just locks up for anywhere from a few seconds to a few minutes, but sometimes it never comes back, and usually after a few seconds users will just force quit and relaunch rather than sit around waiting to see what happens).Īlso note that this occurs regardless of where the client is being run. When running a query that returns a lot of data to the client (hundreds of columns, thousands of rows) user will return periodically to the workbench window, and occasionally when he does so Workbench will be locked up (seems to have happened in background) When the Client Connections window is open and set to refresh periodically (to track query status while doing other work). When expanding an item in the Schemas pane (say, to view the list of tables within a schema) When writing a query in the query window and Workbench appears to be attempting to generate an auto-complete list Doug Taylo We've tried upgrading to 6.1.7, but no real change of behavior.Įxamples of when we've had it lock up (multiple users experiencing similar symptoms):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |