Bug #46304 Unhandled glibmm exception results in forced exit
Submitted: 20 Jul 2009 11:44 Modified: 4 Sep 2009 10:16
Reporter: Craig Fowler Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.1.17 OS:Linux (Kubuntu Jaunty using (new Ubuntu 9.04) .deb installer - 32 bit)
Assigned to: CPU Architecture:Any

[20 Jul 2009 11:44] Craig Fowler
Description:
I discovered this one somewhat by accident.  Workbench forcibly closes due to an unhandled glibmm exception if the mousewheel is used to switch between tabs in the properties pane.  STDOUT output will be attached.

How to repeat:
Open or create a new model, add a table to the model and then double-click that table so it's properties pane shows at the bottom of the model.

Mouse-over the tab bar at the bottom (Tables, Columns, Indexes etc) and use the mousewheel (which has the effect of switching tabs).

Workbench switches tabs, then a split-second later it closes without saving.
[20 Jul 2009 11:45] Craig Fowler
STDOUT created when this bug is reproduced

Attachment: workbench-log-2009-07-20_12.35.txt (text/plain), 3.33 KiB.

[20 Jul 2009 12:07] MySQL Verification Team
I couldn't repeat the behavior reported on Ubuntu 9.04 64-bit.
[20 Jul 2009 12:15] Craig Fowler
Probably worth saying I'm using x86 then ;)
[27 Jul 2009 5:53] Susanne Ebrecht
Hello Craig,

I have ubuntu jaunty (9.04) 32bit here. But I wasn't able to reproduce it. Scrolling with mouse wheel works fine here.

It looks like that it is really Kubuntu related.

Anyway, for deeper analysis we would need the core dump.
[24 Aug 2009 14:43] Craig Fowler
Hi, would like to confim that this bug also affects 5.1.17 but I also noticed that I missed out some information in "how to reproduce" the bug, namely I can't get WB to crash on the 'first open' of the table-edit pane.

So - to revise my "how to reproduce" instructions:

1) Open WB and create a new project
2) Add a new table to that project (either by creating it in the project main view or by creating a new ER diagram and adding the table visually).
3) Edit that table and accept the default name (`table1` in my case)
4) Go to the columns tab and accept the name of the first column (`table1_id` in my case)
5) Close the edit pane for table1
6) Re-open the edit pane by double-clicking the table in either the diagram or in the list of tables
7) Use the mousewheel to scroll through the tabs Table/Columns/Indexes

The crash occurs at this point.  Without closing and re-opening the table-edit pane I discovered that I can't reproduce it either.
[26 Aug 2009 4:06] MySQL Verification Team
Verified following instructions in the reporter's last comment on Ubuntu 9.04 64-bit and 5.1.17.

(mysql-workbench-bin:4864): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: invalid index

aborting...
Aborted
miguel@luz:~$
[27 Aug 2009 7:19] Maksym Yehorov
Fixed
[28 Aug 2009 22:37] Johannes Taxacher
fix confirmed. will be included in 5.1.18
[4 Sep 2009 10:16] Tony Bedford
An entry has been added to the 5.1.18 changelog:

MySQL Workbench generated an exception when the mouse wheel was used to move between tabs in the Table Editor:

(mysql-workbench-bin:4864): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion
`node != NULL' failed

glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: invalid index

aborting...
Aborted