Bug #72329 Creating new table causes seg fault
Submitted: 13 Apr 2014 4:28 Modified: 14 May 2014 17:17
Reporter: Bacil Warren Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:6.1.4.11773 OS:MacOS (10.9.2)
Assigned to: CPU Architecture:Any

[13 Apr 2014 4:28] Bacil Warren
Description:
Upon creating a new table, "Index out of bounds" error displays and MySQL Workbench crashes with Segmentation Fault error.

Log files will be added after creation.

How to repeat:
I have three of these crashes tonight alone, and it's about 80% consistent with creating a new table. Whether using the "Place new table" item in the EER diagram tab, or double-clicking "Add Table" under "Physical Schemas" in the Model tab, creating a new table crashes with the same "Index out of bound" error resulting in a Segmentation Fault error and application crash.
[13 Apr 2014 20:07] MySQL Verification Team
Thank you for the bug report. Please elaborate how the crash happens when
adding a table. Maybe I am missing a particular action when adding;creating a
table. Thanks.
[14 Apr 2014 0:04] Bacil Warren
The crash happens after I add a table, regardless of how. After adding the table, about 80% of the time I get a dialog box that says "Index out of bounds" and then about 80% of the time that happens, the application crashes with a Segfault error. I'll attach a .MOV file in a moment.
[14 Apr 2014 0:19] Bacil Warren
Naturally, now that I'm recording the screen, it won't crash. I'll try again later.
[15 Apr 2014 2:23] Bacil Warren
Twice today, I have gotten the "index out of range" error without a crash. Both times, it happened after I created a new table, after having created a foreign key in the table I created immediately prior to it. I will try this again with a brand-new ERD/model file and see if the behavior is repeatable.

So, the steps to reproduce seem to be:
- create a table
- create some fields
- create at least one FK
- create a new table, which results in the "index out of range" error
[15 Apr 2014 2:32] Bacil Warren
Confirmed. Don't even have to do anything with the FK, however; merely opening the table with an existing FK and creating a new table causes the error. I do believe that the severity can perhaps be downgraded to S3, since it doesn't appear to be crashing the Workbench app at the moment, though it has in the past.

Steps to reproduce:
- Open new document
- Create two new tables, with fields in each
- Link one to the other with a FK
- Create a new table, error "Index out of range" appears. Click "Ok" to dismiss error
- double-click on table WITHOUT FK, then create a new table, and note no error message
- double-click on table WITH FK, and create new table. Error "Index out of range" appears again.
[15 Apr 2014 2:38] Bacil Warren
After continued testing, the error message appears even when simply switching to another table, when the table with a FK is open and the FK tab is visible.

- Double-click on any table without a FK to edit fields
- double-click on table with FK and select "Foreign Keys" tab
- double-click on existing table, or create new table; error "Index out of range" appears.

QT movie to follow.
[21 Apr 2014 19:25] MySQL Verification Team
out of range

Attachment: out_of_range.png (image/png, text), 56.16 KiB.

[21 Apr 2014 19:26] MySQL Verification Team
Thank you for the feedback.
[23 Apr 2014 8:45] Jan Lender
I've experienced the behaviour as described by Bacil Warren  [14 Apr 0:04]. Env: MySQL Workbench 6.1 Community, version 6.1.4.11773 build 1454. OS:  OS X 10.9.2. Report's been sent each time.
Jan
[25 Apr 2014 17:47] Alfredo Kojima
Bacil, thanks a lot for the narrowed down step by step, that is really appreciated.
[14 May 2014 17:17] Philip Olson
Fixed as of the upcoming MySQL Workbench 6.1.6 release, and here's the changelog entry:

The following scenario generated a segmentation fault in the EER diagram
editor: Double-click a table with a FK, double-click a table with a FK,
select the "Foreign Keys" tab, and to generate the "Index out of range"
error and segfault, either double-click an existing table or create a new
table.

Thank you for the bug report.