Bug #60426 | WB crash on selecting rows | ||
---|---|---|---|
Submitted: | 11 Mar 2011 3:55 | Modified: | 27 May 2011 14:46 |
Reporter: | Yinyin Liao | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.32, 5.2.33 | OS: | Linux (ubuntu 10.04 (32-bits, i686)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
[11 Mar 2011 3:55]
Yinyin Liao
[11 Mar 2011 4:01]
Yinyin Liao
here is the error message copied from terminal, full dump file is attached. tried to increase logging level to have more verbose error message but without luck: ---- glibmm-ERROR **: unhandled exception (type unknown) in signal handler aborting... Aborted ----
[11 Mar 2011 10:36]
MySQL Verification Team
I couldn't repeat on Linux Mint 10 X86_64.
[12 Mar 2011 16:45]
Yinyin Liao
architecture of my CPU is i686 (ubuntu 10.04 32-bits) downgraded to 5.2.30 resolved this problem. (5.2.31 have random crashes)
[13 Mar 2011 9:46]
Valeriy Kravchuk
So, this looks like a regression bug. Can you, please, try to check if recent version, 5.2.33, is also affected in your case.
[14 Mar 2011 7:35]
Yinyin Liao
upgrade to 5.2.33 (MySQL Workbench CE 5.2.33 7506) but have same problem. WB crashes with the following messages: ---- glibmm-ERROR **: unhandled exception (type unknown) in signal handler aborting... Aborted ----
[14 Mar 2011 10:50]
MySQL Verification Team
That happens on your side all the times or in randomly way?. I was able to repeat 1 time and I wasn't able to repeat again.
[14 Mar 2011 18:15]
Yinyin Liao
it happens all the time in my side.
[27 Apr 2011 14:46]
MySQL Verification Team
I have tested on another OS/Environment without to repeat, if that happens with specific table please provide its create table statement?. Thanks in advance.
[27 May 2011 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".