Bug #91371 Mysql Workbench crashes on table primary key change
Submitted: 22 Jun 2018 11:16 Modified: 29 Jun 2018 21:08
Reporter: Timofey Vorobyov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.3.8 build 1228, 8.0.11 OS:Ubuntu (18.04 LTS)
Assigned to: CPU Architecture:Other (x64)
Tags: crash

[22 Jun 2018 11:16] Timofey Vorobyov 
Description:
Mysql workbench crashes when I attempt to add a column to an existing multi-column index (primary key) of a table. No workaround within Workbench (apart from manual SQL coding which I have not tried) is possible.

How to repeat:
Steps:
1. have a table with multi-column primary key defined
2. add a column to the table using table editor (OK)
3. Go to Indexes tab
4. Select primary key
5. Click the newly created column to add it to the index.

Suggested fix:
N/A
[22 Jun 2018 12:47] MySQL Verification Team 
Thank you for the bug report. Which exactly version are you using 6.3.10? Try the development release 8.0.11 rc too. Thanks.
[22 Jun 2018 12:48] Timofey Vorobyov 
updated version info
[22 Jun 2018 12:49] Timofey Vorobyov 
updated OS version
[22 Jun 2018 12:51] Timofey Vorobyov 
apt reports version number as: 6.3.8+dfsg-1build3
[22 Jun 2018 15:17] Timofey Vorobyov 
On version 8.0.11 (latest communtity rc), behavior is different: the program does not crash, but clicks on column checkboxes to change index columns are ignored.
[23 Jun 2018 8:07] MySQL Verification Team 
When I'm attempting exact steps, I'm experiencing 5/5 times crash even with WB 8.0.11(apt repo installed WB 8.0.11-rc). Could you please confirm the stack traces if it is same issue? Joining the logs shortly.

###
ushastry@BionicBeaver:~$ mysql-workbench --log-level=debug3
Found /usr/lib/x86_64-linux-gnu/libproj.so.12
Logger set to level 'debug3'. '1111111'
Ready.

## Connecting a remote instance using Standard TCP/IP over SSH Connection Method.

CREATE TABLE `new_table` (
  `id` int(11) NOT NULL,
  `col1` varchar(45) DEFAULT NULL,
  `col2` varchar(45) NOT NULL,
  `col3` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;

Alter table -> ensure that 'col3' column is selected -> click "Indexes" tab <-- Click on col3's length column and make sure 0 is selected and then attempt to click on "col3" text or even checkbox will trigger crash.

Thanks,
Umesh
[23 Jun 2018 8:08] MySQL Verification Team 
test results

Attachment: 91371.result (application/octet-stream, text), 212.67 KiB.
[25 Jun 2018 16:32] Timofey Vorobyov 
mysql-workbench dump

Attachment: mysql-wb.log (text/x-log), 105.47 KiB.
[25 Jun 2018 16:37] Timofey Vorobyov 
Tried to repeat the case. When the table is new, the program sometimes works, sometimes - crashes.

See attached dump
[26 Jun 2018 6:29] MySQL Verification Team 
Thank you for confirming, seems to me the same crash in 8.0.11 as well.

Regards,
Umesh
[29 Jun 2018 21:08] Christine Cole 
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.12 release, and here's the changelog entry:

An attempt to add a column to an existing multicolumn index (primary key)
of a table caused MySQL Workbench to stop working.

Thank you for the bug report.