Bug #56009 Forward engineering model crashes WB

• Submitted: 16 Aug 2010 12:18
• Modified: 3 Sep 2010 16:14
• Reporter: Karsten Wutzke
• Status: Closed
• Category: MySQL Workbench: Modeling
• Severity: S1 (Critical)
• Version: 5.2.26
• OS: Windows (7)
• Assigned to: Alfredo Kojima
• CPU Architecture: Any
• Tags: crash, forward engineering

[16 Aug 2010 12:18] Karsten Wutzke

Description:
Forward engineering a model crashes WB.

How to repeat:
Try the attached model.

[16 Aug 2010 12:20] MySQL Verification Team

Thank you for the bug report. Please attach the model. Thanks in advance.

[16 Aug 2010 12:21] MySQL Verification Team

Please disregard my prior comment.

[16 Aug 2010 12:24] MySQL Verification Team

Verified on Fedora 13 X86_64.

[18 Aug 2010 11:00] Karsten Wutzke

I uploaded a smaller model which also crashes version 5.2.25 which I'm currently working with. Please fix this bug ASAP.

[25 Aug 2010 16:46] Alfredo Kojima

Fixed.

As a workaround, empty the customData dict that contains another dict (catalog.customData.hibernateExport... in the 2nd model) when doing forward engineer.

[26 Aug 2010 10:19] Johannes Taxacher

fix confirmed in repository

[1 Sep 2010 16:31] Tony Bedford

An entry has been added to the 5.2.27 changelog:

Forward engineering a model to a live database crashed MySQL Workbench.

[3 Sep 2010 16:14] Karsten Wutzke

Question: did you change the policy when plugins are saving to customData, so that the user is *not* notified of changes when exiting the model? I don't like it...