Refer: http://www.webyog.com/forums/index.php?showtopic=6208 & IB ticket 63449

Both complain about situaations where the GUI is irresponsible because a background thread is. The GUI thread is 'hijacked by' the irresponsvie backgorund thread. In the Forums post I added a simple test case myself

--- 1st connection

USE TEST; DROP TABLE IF EXISTS t1; CREATE TABLE t1 (id INT); INSERT INTO t1 values (1) LOCK TABLES t1 READ;

-- 2nd connection

-- a: -- execute from editor USE TEST; UPDATE t1 SET id = 2 WHERE id = 1; -- it hangs (waits for LOCK to be released), but I can stop query from the 'X* icon

-- b: --- perform same operation from GUI (DATA or RESULT tab) -- still hangs and cannot be stopped -- switching connection tabs hangs SQLyog completely.

Even though the cases are different the underlying reason is the same in all the cases: GUI thread is 'locked' or 'hijacked' by background thread.

Also see IB 108021

This is actually supposed to be fixed (somewhere in 10.x I believe), but we received a new report (in ticket 167794) that needs to be analyzed before we can close here.