Bug #57139 | Workbench encountered a bug (againagainagain) | ||
---|---|---|---|
Submitted: | 30 Sep 2010 13:16 | Modified: | 6 Oct 2010 11:38 |
Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.28 | OS: | Any (Windows XP Sp3) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
Tags: | qc |
[30 Sep 2010 13:16]
Peter Laursen
[30 Sep 2010 13:54]
Valeriy Kravchuk
I was able to repeat this while working on Bug #57137 and trying to EDIT random tables on local 5.1.51 server, some with PK and some without. So there is definitely something to fix here.
[1 Oct 2010 8:04]
Mike Lischke
I cannot reproduce this problem whatever I try. Without a reproducible test case nobody can do anything meaningful with that report.
[1 Oct 2010 8:09]
Peter Laursen
Try harder then (on different systems etc.)! Valeriy was able to reproduce it. The actual table was this one: /* SQLyog Ultimate v8.61 MySQL - 5.1.51-community : Database - test ********************************************************************* */ /*!40101 SET NAMES utf8 */; /*!40101 SET SQL_MODE=''*/; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; USE `test`; /*Table structure for table `111111` */ DROP TABLE IF EXISTS `111111`; CREATE TABLE `111111` ( `id` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; /*Data for the table `111111` */ insert into `111111`(`id`) values (1); insert into `111111`(`id`) values (2); /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; Opening the editor to this table multiple times will sooner or later crash WB on my system.
[1 Oct 2010 9:55]
Peter Laursen
Here we have another one that may not be reproducible in 'first shot': http://bugs.mysql.com/bug.php?id=57150 I think that is one problem with WB that due to its complexity (many 'layers' - in .NET/MONO, C++, Python, different graphics-routines (OpenGL or not) for different system etc) it is hard do reproduce and debug issues consistently and systematically. But that architecture was your choice so you - and not I - will have to 'bear the brunt' of it. At least two people (Valeriy and I) encountered this the same day so there is a problem. That is indisputable.
[1 Oct 2010 14:00]
Alfredo Kojima
Madly clicking Execute on EDIT sakila.film will produce the crash.
[1 Oct 2010 14:06]
Peter Laursen
hehe! In my case it does not need to be 'madly' :-) - just doing 'quietly' 4-5 times will most often do!
[1 Oct 2010 16:57]
Alfredo Kojima
fixed
[5 Oct 2010 13:42]
Johannes Taxacher
fix confirmed in repository (tried madly and quietly ;)
[6 Oct 2010 11:38]
Tony Bedford
An entry has been added to the 5.2.29 changelog: Attempting to open the Table Editor in the SQL Editor multiple times for a table that contained no primary key caused MySQL Workbench to crash.