Bug #64665 | MySQL Workbench Crash | ||
---|---|---|---|
Submitted: | 15 Mar 2012 23:25 | Modified: | 30 Apr 2012 13:45 |
Reporter: | Russell T | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S2 (Serious) |
Version: | 5.2.38CE Revision 8753 | OS: | Windows (Win 7 64 bit) |
Assigned to: | CPU Architecture: | Any |
[15 Mar 2012 23:25]
Russell T
[15 Mar 2012 23:31]
Russell T
Have a look at the attached screenshot, and down the bottom you can see two columns I was adding "nullable_junk_column" and "not_nullable_junk_column". The crash occurred after I had typed "INT" as the data type for "not_nullable_junk_column", and clicked on "NN" with my mouse to make that column not nullable.
[16 Mar 2012 2:15]
Russell T
MySQL Workbench crashed again, this time the cause was: 1. Add a Diagram in an existing model 2. Pressed F2 to rename the Diagram 3. Typed the new diagram name 4. Pressed the "Enter" key, then the Workbench crashed
[16 Mar 2012 14:14]
MySQL Verification Team
Adding a Diagram plus F2 rename and Enter doesn't crash for me.
[19 Mar 2012 22:44]
Russell T
It crashed again when re-ordering columns within a table. Problem signature: Problem Event Name: APPCRASH Application Name: MySQLWorkbench.exe Application Version: 5.2.38.8753 Application Timestamp: 4f43fc17 Fault Module Name: StackHash_0a9e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 063d334c OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 3081 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
[31 Mar 2012 13:45]
Valeriy Kravchuk
Can you upload any .mwb file that demonstrates the problem?
[1 May 2012 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".