Bug #92718 Not responding right after start executing a query!
Submitted: 9 Oct 2018 11:31 Modified: 10 Oct 2018 11:33
Reporter: Konstantinos P. Moschovis Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.10 CE build 12092614 (64 bit) OS:Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:Any (6.3.10 CE build 12092614 (64 bit))
Tags: WBBugReporter

[9 Oct 2018 11:31] Konstantinos P. Moschovis 
Description:
After opening MySQL Workbench and connect on local or a remote MySQL server, right after setting a query to execute stops responding. I have to wait for a couple of minutes to complete the query, and gain control of MySQL Workbench.

This is really annoying, since i use MySQL Workbench almost everyday for administration purpose to mote than 1 databases. It costs time and as further result money.

----[For better reports, please attach the log file after submitting. You can find it in C:\Users\user\AppData\Roaming\MySQL\Workbench\log\wb.log]

How to repeat:
After opening MySQL Workbench and connect on local or a remote MySQL server, right after setting a query to execute stops responding. I have to wait for a couple of minutes to complete the query, and gain control of MySQL Workbench.
[9 Oct 2018 11:32] Konstantinos P. Moschovis 
Log of reported Bug

Attachment: wb.7z (application/octet-stream, text), 377.64 KiB.
[9 Oct 2018 11:41] MySQL Verification Team 
Thank you for the bug report. I couldn't repeat with latest version 6.0.12.
[9 Oct 2018 12:02] Konstantinos P. Moschovis 
@Miguel Solorzano, I know that you can't refactor the issue/bug. But why do you use Workbench 6.0.12?
[9 Oct 2018 12:03] MySQL Verification Team 
Sorry I did a typo I meant 8.0.12 the last version.
[9 Oct 2018 12:13] Konstantinos P. Moschovis 
Could it be, by any chance, the version of MySQL server(5.6.40-log, local, 5.6.19-log remote) responsible for that?
[10 Oct 2018 11:33] Konstantinos P. Moschovis 
After testing the case using MySQL Workbench versions 6.1.7 and 6.2.5, surprisingly I found out that there is no problem at all. Well I thought that by upgrading i should have better functionality, but seems like downgrading is the better option.
I had tried upgrading to 8.0.12 by came up with exactly the same issue.

So for now and till Oracle Developers found a solution on the reported bug, because there are many reports on the exactly same problem, i will stick on 6.2.50. 

Thank you for any suggestion, time and effort you spend on this bug report.
For any other facing the same issue, for now the best solution is, sadly, downgrading.