Bug #70376 | Intermittent: "MySQL Connections" connection list is non-responsive to clicks | ||
---|---|---|---|
Submitted: | 18 Sep 2013 11:54 | Modified: | 10 Sep 2014 4:19 |
Reporter: | Craig Fowler | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.0.7.11215 | OS: | Linux (Debian Stable +libc6 from testing) |
Assigned to: | CPU Architecture: | Any | |
Tags: | UI |
[18 Sep 2013 11:54]
Craig Fowler
[18 Sep 2013 12:26]
MySQL Verification Team
Thank you for the bug report. Which kind of connection local/remote ?. Thanks.
[18 Sep 2013 13:40]
Craig Fowler
When it does happen, it occurs with either types of connection, remote and/or local. As far as I can see, it seems to be that it is the UI which is not responding to the click, and not even attempting to initiate the connection. If that's the case then the actual details of the connection are unlikely to be of any relevance.
[18 Sep 2013 14:19]
Peter Laursen
Looks like the thread executes code when this happens. Maybe this code execution should be in another thread (if I am right)?
[19 Sep 2013 11:56]
Craig Fowler
Something else I have noticed - when this affects me (as it has just again) is that the top-right corners of the connection tiles (which should lead to the management UI) are also unresponsive. When hovering the mouse over the top-right of the connection tiles, they do change state to show the "tear away" effect, but on clicking on that tear the whole tile reverts to its normal mouse-off state and the connection management/detail UI does not open. The tile stays in this state as long as the mouse is not moved. When the mouse is moved again over the tile it reverts back to its mouse-over state (including the tear-away effect if the mouse is in the top-right of the tile). For clarification: When this bug affects me, it does not matter which connection I click on. every one of the tiles exhibits the same behavior. Also, this is not an application hang - the application as a whole is still responsive (I can switch from the home screen tab to an open model tab and back again for example, indeed sometimes doing this fixes the UI bug and allows me to click connections again). It just seems that the connection-tiles UI can get into an invalid state under which they won't accept clicks.
[28 Jan 2014 11:01]
Craig Fowler
I have upgraded WB to 6.1.1.11562 build 1158 (using the .deb installer package for Ubuntu 12.x). I can still reproduce this issue, although as always it's intermittent. I haven't been able to reproduce it at-will nor can I find any circumstances that appear to make it more or less reproducible.
[3 Mar 2014 10:34]
Craig Fowler
Here is some information retrieved via GDB immediately after reproducing this issue: The steps to retrieve it were 1) <see the issue> 2) Attach gdb to the workbench-bin process 3) "set backtrace limit 5" (within gdb) 4) "t a a bt" (within gdb) The output of this is: --- Thread 2 (Thread 0x7f09739ab700 (LWP 6513)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x00007f098021b5f5 in g_cond_wait_until () at /tmp/buildd/glib2.0-2.36.4/./glib/gthread-posix.c:865 #2 0x00007f09801b2941 in g_async_queue_pop_intern_unlocked () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f09801b2ecb in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f0983d9e9ea in bec::GRTDispatcher::worker_thread(void*) () from /usr/lib/mysql-workbench/libwbpublic.so Thread 1 (Thread 0x7f09850a79c0 (LWP 6511)): #0 0x00007f097c63395d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f09801dc194 in g_main_context_iterate.isra.22 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f09801dc5fa in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f097f78e797 in IA__gtk_main () at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmain.c:1256 #4 0x00000000006a57a3 in main ()
[10 Sep 2014 4:19]
Alfredo Kojima
We believe this was fixed in 6.1, if the problem still occurs, please reopen the bug.