Bug #66133 | Crash after adding column to table and viewing inserts | ||
---|---|---|---|
Submitted: | 1 Aug 2012 1:29 | Modified: | 1 Aug 2012 12:23 |
Reporter: | Ben Lambell | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S1 (Critical) |
Version: | 5.2.41 | OS: | Windows (Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[1 Aug 2012 1:29]
Ben Lambell
[1 Aug 2012 1:39]
Ben Lambell
I should note - this error report was triggered by an exception while I was trying to reproduce the bug actually being described. Ie, the stack trace isn't directly related to the bug I'm describing, although it shows the right system info. I'm fairly sure the exception was indirectly caused by the bug.
[1 Aug 2012 2:16]
Ben Lambell
Ah, okay, I have successfully reproduced the bug (I think). Download my model file from http://tensitygames.com/EWE.mwb and put it in the workbench. Perform the following: - Open the model - Edit the table `security` and add the following columns: - x (TINYINT, NOT NULL) - y (TINYINT, NOT NULL, DEFAULT 2) - Save the model file - Click on the 'inserts' tab to view inserted rows in `security` - Double click on the 'itemtype' table - Close the table - Double click on the security table - Double click on the itemtype table, twice (it will not open) - Right click on the itemtype table and select 'edit table', three times (it will not open) - Right click on the itemtype table and select 'edit table in new window' (it will not open) - Close the model - Close the workbench - Open the workbench. It will fail to launch, stating "Failed to read from an IPC Port: The pipe has ended" Sorry for the convoluted directions, they are the best I could come up with to reproduce the error (I'm not really that experienced)
[1 Aug 2012 4:17]
Valeriy Kravchuk
Looks like a duplicate/kind of bug #66013. Please, check.
[1 Aug 2012 7:52]
Ben Lambell
Ah, I think you're right, what I've managed to replicate here is bug #66013. I'm not sure whether the other crashes I've had are related to #66013 or not, but in any case, I haven't been able to replicate them, so I'm going to assume they are. Thanks for the quick response. I suggest someone delete this report or mark it as closed, whichever is appropriate (I don't know).
[1 Aug 2012 12:23]
MySQL Verification Team
Thank you for the feedback. Duplicate of http://bugs.mysql.com/bug.php?id=66013.