Bug #73023 | Workbench crash on MySQL over SSH tunnel | ||
---|---|---|---|
Submitted: | 17 Jun 2014 14:26 | Modified: | 3 Jul 2014 11:22 |
Reporter: | James Withers | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 6.1.6 | OS: | Windows (8.1 Pro x64) |
Assigned to: | CPU Architecture: | Any |
[17 Jun 2014 14:26]
James Withers
[17 Jun 2014 16:30]
MySQL Verification Team
Thank you for the bug report. Against which MySQL Server are you connecting and remote OS (I couldn't repeat connecting with 5.6.19 running on OSX 10.9). Thanks.
[24 Jun 2014 6:33]
László Somogyi
Hello It is the same for me from Win7 64 bit and to mysql 5.5.37 over ssh on a debian. Tried to downgrade to workbench 6.1.4, but thats even worse... before i never had this kind of problem, but didnt try to downgrade further. This happens very often and then it is impossible to open the table for editing, even after restart (other tables would still work, but the one that crashed, will constantly crash). When i get lost connection during query, i can do anything (reconnect to rdbms icon), the next query will crash the whole program... and the lost connection is strange anyway, it is really common when i try to select from another db - in the same connection - than from last time, but comes random too. This is really critical...
[3 Jul 2014 11:20]
James Withers
This appears to be resolved in 6.1.7.11891 build 1788
[3 Jul 2014 11:22]
MySQL Verification Team
Thank you for the feedback.