Bug #72507 | Repeated crashing of Workbench 6.1 on two different servers | ||
---|---|---|---|
Submitted: | 1 May 2014 21:14 | Modified: | 22 May 2014 14:48 |
Reporter: | Martin O'Shea | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 6.1.4 | OS: | Windows (Microsoft Windows 7 Service Pack 1 build 7601, 32-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[1 May 2014 21:14]
Martin O'Shea
[1 May 2014 21:15]
Martin O'Shea
This issue has been raised in the MySQL Workbench forum at: http://forums.mysql.com/read.php?152,613226,613226
[1 May 2014 22:28]
MySQL Verification Team
Thank you for the bug report. Please elaborate in number of word 'several': have several thousand tables, each of which may contain several hundred columns. Thanks.
[1 May 2014 23:10]
Martin O'Shea
Concerning my use of the term 'several', one particular schema of mine stores some 4700 tables. About 4500 of these are made up of up to 600 columns and approximately 15000 rows. Workbench fails when this schema is queried, but this occurs only when the tables for the schema are loaded into the Navigator.
[14 May 2014 15:04]
Philip Nelson
I am having the same issue. I have narrowed it down to the connection using ssl if available option in the connection. With the ssl option I get app crash consistently. Without I don't crash, but sometimes get Error Code: 2013 Lost connection to MySQL server during query. In my case it is happening querying an Amazon RDS instances. These same instances all worked with this version of workbench for the prior 2 days when I installed it. Other users with an earlier 6.1 version of workbench are fine, and users are also fine with a 6.0 version, all using ssl.
[14 May 2014 22:36]
Martin O'Shea
I don't have need to use SSL normally when connecting to Workbench. I am administrator of my two servers and I also log into Workbench as 'root' anyway. But I have just tried SSL in my connections to Workbench and my queries continue to fail, even for tables with only a few hundred records. As before, Workbench simply crashes with: 23:06:02 [INF][ WQE backend]: Found auto-save workspace C:\Users\madmin.rzone.000\AppData\Roaming\MySQL\Workbench\sql_workspaces\Local_instance_MySQL-2.autosave 23:06:02 [INF][ WQE backend]: Found auto-save workspace C:\Users\madmin.rzone.000\AppData\Roaming\MySQL\Workbench\sql_workspaces\myDataSharer-1.autosave 23:06:02 [INF][ WQE backend]: Found auto-save workspace C:\Users\madmin.rzone.000\AppData\Roaming\MySQL\Workbench\sql_workspaces\visualRSS-1.autosave 23:06:02 [INF][ Workbench]: UI is up 23:06:03 [INF][ Workbench]: Running the application 23:06:15 [INF][ SSH tunnel]: Starting tunnel 23:06:16 [ERR][ GRTDispatcher]: exception in grt execute_task, continuing: Exception: Access denied for user 'root'@'localhost' (using password: NO) 23:06:16 [INF][ WQE.net]: Launching SQL IDE 23:06:18 [INF][ WQE.net]: SQL IDE UI is ready 23:13:36 [ERR][ AutoCCache]: Exception during update of cache for 'schemaA _dm_19284_591305_07112013_1383849338694_keyword_frequencies': Malformed packet 23:13:45 [ERR][ AutoCCache]: Exception during update of cache for 'schemaA _dm_19366_349975_13112013_1384362718663_keyword_frequencies': Malformed packet The data in both of the tables referred to in the messages above appears to be intact. So for the moment I am using Query Browser.
[22 May 2014 14:48]
Marcin Szalowicz
This is a duplicate of bug #72486
[25 Jun 2014 13:02]
Robert Mouat
I am seeing similar problems. I am running 6.1.6 on windows 7 64bit with 8GB RAM. I am connecting to MySQL 5.1.69 hosted on Amazon RDS. I get a repeatable crash by doing the following: * start workbench * connect to database as root (using SSL and password) * 'use myschema' * 'select * from MYTABLE' I have a workaround. It doesn't crash if I run 'desc MYTABLE' before the select query. In the logs I see a dozen errors of the form: 13:44:52 [ERR][ AutoCCache]: Exception during update of cache for 'myschema MYTABLE': Insufficient memory: cannot create MySQL handle using mysql_init()
[30 Sep 2014 16:17]
wes romero
I am also facing the same issue when running MySQL Workbench. I'll run a simple SELECT * FROM Table1 WHERE Column1 = 'email@email.com'; and then it will crash. Faulting application name: MySQLWorkbench.exe, version: 6.1.6.11834, time stamp: 0x53729aea Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7 Exception code: 0xc0000005 Fault offset: 0x000337a2 Faulting process id: 0x1090 Faulting application start time: 0x01cfdcc88c67d2e9 Faulting application path: C:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\MySQLWorkbench.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: d9a507ca-48bb-11e4-ac22-5c514f932154 Application: MySQLWorkbench.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 772E37A2 Stack: