Bug #76759 Workbench for Windows Crashes When Correcting an Insert Problem

• Submitted: 20 Apr 2015 15:51
• Modified: 20 Apr 2015 16:20
• Reporter: Gene Rodrigues
• Status: Can't repeat
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 6.0.8.11354 Build 833
• OS: Windows (7 (Latest))
• CPU Architecture: Any
• Tags: crash grid insert

[20 Apr 2015 15:51] Gene Rodrigues

Description:
After returning to the insert grid after identifying a record insert problem during reverse engineering, Workbench sometimes crashes or displays a dialog indicating it has crashed. However in many cases, the program has not crashed, does not shutdown as indicated and one can continue to work on inserts until it does crash many operations later. 

How to repeat:
I have been working on a l10n module with tables containing foreign key constraints and have been experiencing these crashes hundreds of times per day due to the large number of inserts. The crashes occur when attempting to select the column containing the erroneous data after a failed reverse engineering run. As soon as one clicks the field in the grid, the crash occurs. 

I know the tables themselves as well as the foreign key relationships are correct because the end product does view, create, update and delete correctly.

Suggested fix:
Because of some unrelated problems resulting in odd grid behavior that I will report shortly, I think the grid widget is the source of the problem.

[20 Apr 2015 16:20] MySQL Verification Team

Thank you for the bug report. Your version 6.0.8 is quite older please update to 6.2.5 or 6.3.2 rc. Thanks.