Bug #44340 Deleting/cutting relation from diagram crashes MySQL Workbench

Submitted: 17 Apr 2009 8:19 Modified: 8 Jun 2009 15:47
Reporter: Martin Koch Andersen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.1.10a OS:MacOS
Assigned to: Johannes Taxacher CPU Architecture:Any
Tags: CHECKED

[17 Apr 2009 8:19] Martin Koch Andersen
Description:
Deleting or cutting a relation from a diagram often crashes MySQL Workbench.

How to repeat:
See model:
http://925.dk/public/mbb.mwb

Go to the diagram and either:

1) Cut the "vi_phone_no" relation.
or
2) Delete the "vi_phone_no" relation (but keep in model).

- and woila crash.
[17 Apr 2009 16:53] Valeriy Kravchuk
Thank you for the problem report. Do you get the crash every time you delete one of the relationships? What version of Mac OS X do you use? 

In my case Cut is disabled, by the way, and I was able to get a crash after delete and some other manipulations only once on 10.5.6.
[21 Apr 2009 10:39] Martin Koch Andersen
Yes, each time I delete/cut the "vi_phone_no" relation it crashes.
Using MAC OS X 10.5.6.

I right click the relation, and select delete or cut. And they are not grayed out (and why would they be).

I use the Workbench version that is available from here http://dev.mysql.com/downloads/workbench/5.1.html as Mac OS X 10.5 Intel (DMG) 5.1.10a.
[21 Apr 2009 16:06] Valeriy Kravchuk
I've got a repeatable crash at least after double-clicking one of the relationships to view/edit it more than once. We definitely have a problem here.
[15 May 2009 8:30] Martin Koch Andersen
This seems fixed (or not an issue) in the latest beta version.
[3 Jun 2009 21:11] Johannes Taxacher
Cut is properly disabled now (theres no cut/copy/pasting of relations).
deleting the FKs doesnt crash WB.
[8 Jun 2009 15:47] Tony Bedford
An entry was added to the 5.1.13 changelog:

Deleting or cutting a Relation from an EER diagram crashed MySQL Workbench.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.