Bug #71810 | Workbench crash creating new index on a table | ||
---|---|---|---|
Submitted: | 23 Feb 2014 17:46 | Modified: | 15 Mar 2016 16:09 |
Reporter: | Pero Trenq | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.0 build 6.0.7.11215 | OS: | Linux (arch linux) |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash, INDEX |
[23 Feb 2014 17:46]
Pero Trenq
[24 Feb 2014 6:34]
MySQL Verification Team
Hello Pero, Thank you for the report. I tried to reproduce this issue with GA release on OL6, Win7 but couldn't reproduce. Could you please check if it is repeatable on GA release i.e on MySQL Workbench 6.0.9 ? Or with Dev release MySQL Workbench 6.1.1 beta? Thanks, Umesh
[25 Mar 2014 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".
[2 Mar 2015 21:52]
James Tyranski
I have the same issue with version 6.2.4.12437 build 2426 (64 bit) Community.
[2 Mar 2015 22:00]
James Tyranski
MySQL Workbench CE (GPL) 6.2.4 12437 build 2426
Attachment: mysql-workbench_error_dump.txt (text/plain), 80.41 KiB.
[25 Aug 2015 12:07]
MySQL Verification Team
Please try version 6.3.4. Thanks.
[25 Aug 2015 14:14]
James Tyranski
I can confirm this is still happening on 6.3.4 build 828 (64 bit). Just tested now using the same steps provided in earlier comments. -------------------------------- Dell Precision WorkStation T3400 Intel Core 2 Duo (64 bit) 6GB RAM NVidia GeForce GTX 285 Arch Linux 4.1.4-1
[12 Nov 2015 19:08]
Ignacio Nieto
Same on Ubuntu 14.04 LTS and version 6.0.8.11354 build 833
[12 Feb 2016 9:13]
Marcin Szalowicz
Hello James, I couldn't repeat this on 6.3.6, please let me know if that still exists for you. Ignacio, I'm sorry but you're using very outdated version, please upgrade to the latest GA.
[16 Mar 2016 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".