Bug #82187 mysql workbench crashes randomly
Submitted: 11 Jul 2016 18:25 Modified: 22 Feb 2018 0:05
Reporter: mike coutinho Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.3.7 OS:MacOS (10.10.5)
Assigned to: CPU Architecture:Any

[11 Jul 2016 18:25] mike coutinho
Description:
Under normal use, MySQL Workbench crashes.  I haven't been able to determine what I have done or what specifically causes the problems.  I tried to go into the wb.log file, but every time I restart the application, it clears out the file and any information is lost.  I also have tried to keep it open and let the app crash naturally, but after leaving it in a "i am crashing" state for an hour, I had to force quit the application.  

I did not see these problems on the previous point release of 6.3.  I would be happy to submit more information if you would let me know specifically what you would like me to send in.

How to repeat:
Not sure

Suggested fix:
Not sure
[13 Jul 2016 15:13] mike coutinho
i have been running workbench from the command line with --log-level=debug3 and debug4 (not even sure if 4 is a valid option) and tried to capture when workbench crashes on me.  Even when I do this, workbench does not retain any data in the log file.  Crash happens and nothing is added to the log file.  Also, every time I open the app, everything in the previous log file is wiped out and starts again.
[13 Jul 2016 15:29] mike coutinho
I have gotten it to crash repeatedly.  

When in workbench, if I right click on a table in the Shemas window on the left side, it crashes.  The menu comes up and the spinning beach ball of death comes out.
[14 Jul 2016 0:00] MySQL Verification Team
Thank you for the bug report.

Date/Time:       2016-02-28 05:12:14 -0300
OS Version:      Mac OS X 10.11.4 (Build 15E65)
Architecture:    x86_64
Report Version:  22

Command:         MySQLWorkbench
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Version:         6.3.7.CE (1)
Parent:          launchd [1]
PID:             533

Event:           hang
Duration:        1.10s (process was unresponsive for 308 seconds before sampling)
Steps:           11 (100ms sampling interval)

Hardware model:  MacBookPro9,2
Active cpus:     4

Fan speed:       4100 rpm

--------------------------------------------------
Timeline format: stacks are sorted chronologically
Use -i and -heavy to re-report with count sorting
--------------------------------------------------

Heaviest stack for the main thread of the target process:
  10  start + 1 (libdyld.dylib + 13741) [0x7fff837975ad]
  10  NSApplicationMain + 1176 (AppKit + 25708) [0x7fff8fe2546c]
  10  -[NSApplication run] + 682 (AppKit + 249476) [0x7fff8fe5be84]
  10  -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 (AppKit + 295722) [0x7fff8fe6732a]
  10  _DPSNextEvent + 1067 (AppKit + 298746) [0x7fff8fe67efa]
  10  _BlockUntilNextEventMatchingListInModeWithFilter + 71 (HIToolbox + 198063) [0x7fff8b7e85af]
  10  ReceiveNextEventCommon + 184 (HIToolbox + 198263) [0x7fff8b7e8677]
  10  RunCurrentEventLoopInMode + 235 (HIToolbox + 198965) [0x7fff8b7e8935]
  10  CFRunLoopRunSpecific + 296 (CoreFoundation + 560856) [0x7fff85c25ed8]
  10  __CFRunLoopRun + 910 (CoreFoundation + 562382) [0x7fff85c264ce]
  10  __CFRunLoopDoBlocks + 341 (CoreFoundation + 564485) [0x7fff85c26d05]
 <cut>
[20 Jul 2016 20:44] Nikolas Peralta
I'm having this issue too. I remember having this same problem on Ubuntu.

My log file:

16:13:33 [INF][      WBContext]: Parsing application arguments.
16:13:33 [INF][      WBContext]:     /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
16:13:33 [INF][      Workbench]: Starting up Workbench
16:13:33 [INF][      Workbench]: Loading main window
16:13:33 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: /Applications/MySQLWorkbench.app/Contents/Resources
	plugin path: /Applications/MySQLWorkbench.app/Contents/PlugIns
	struct path: /Applications/MySQLWorkbench.app/Contents/Resources/grt
	module path: /Applications/MySQLWorkbench.app/Contents/PlugIns:/Applications/MySQLWorkbench.app/Contents/Resources/plugins
	library path: /Applications/MySQLWorkbench.app/Contents/Resources/libraries
	user data dir: /Users/niko/Library/Application Support/MySQL/Workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No
16:13:33 [INF][      WBContext]: WbContext::init
16:13:34 [INF][            WBA]: Looking for extension modules for WBA...
16:13:34 [INF][            WBA]: 0 extension modules found
16:13:34 [WRN][            grt]: /Applications/MySQLWorkbench.app/Contents/Resources/data/table_templates.xml:21: link 'com.mysql.rdbms.mysql.datatype.timestamp' <object db.SimpleDatatype> key=simpleType could not be resolved
16:13:34 [WRN][            grt]: /Applications/MySQLWorkbench.app/Contents/Resources/data/table_templates.xml:106: link 'com.mysql.rdbms.mysql.datatype.varchar' <object db.SimpleDatatype> key=simpleType could not be resolved
16:13:34 [WRN][            grt]: /Applications/MySQLWorkbench.app/Contents/Resources/data/table_templates.xml:229: link 'com.mysql.rdbms.mysql.datatype.int' <object db.SimpleDatatype> key=simpleType could not be resolved
16:13:34 [WRN][            grt]: /Users/niko/Library/Application Support/MySQL/Workbench/connections.xml:25: link 'E6120432-3061-49A1-94F2-B96157A87A78' <object GrtObject> key=owner could not be resolved
16:13:34 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Mac OS X version 6.3.6 CE build 511 (32 bit)
	Configuration Directory: /Users/niko/Library/Application Support/MySQL/Workbench
	Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
	Cairo Version: 1.10.2
	OS: OS X 10.11.x El Capitan
	CPU: 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 8.00GiB RAM

16:13:34 [INF][    WQE backend]: Found auto-save workspace /Users/niko/Library/Application Support/MySQL/Workbench/sql_workspaces/Cubito-1.autosave
16:14:23 [INF][      SqlEditor]: Opened connection 'Cubito' to MySQL Community Server (GPL) version 5.6.29
16:14:23 [INF][     AutoCCache]: Initializing autocompletion cache for Cubito
16:23:52 [INF][      SqlEditor]: Opened connection 'Prod CL' to Source distribution version 5.5.40-log
16:23:53 [INF][     AutoCCache]: Initializing autocompletion cache for Prod_CL
16:23:54 [ERR][SqlEditorSchemaTree]: Exception querying metadata from mysql.proc, will fallback to SHOW PROCEDURE: Exception: SELECT command denied to user 'cuponcl'@'201.238.223.138' for table 'proc'
16:28:09 [INF][      SqlEditor]: Opened connection 'Cubito' to MySQL Community Server (GPL) version 5.6.29
16:28:09 [INF][     AutoCCache]: Initializing autocompletion cache for Cubito
16:34:00 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: There was an error while applying the SQL script to the database.
16:34:00 [ERR][  GRTDispatcher]: worker: task 'wizard task' has failed with error:.There was an error while applying the SQL script to the database.
[26 Jul 2016 11:49] Milosz Bodzek
Thank you for the bug report. Can you provide steps to reproduce that issue?
[1 Aug 2016 13:39] mike coutinho
the best I can tell you to reproduce what I saw is this:
When in workbench, if I right click on a table in the Shemas window on the left side, it crashes.  The menu comes up and the spinning beach ball of death comes out.
[1 Aug 2016 14:56] Nikolas Peralta
@Milosz Bodzek: sorry but it happens randomly when I execute a query. I can execute an X query and the program crashes. Opening and running the same X query again works perfectly. 

In both cases the query is executed on server.

And I'm having another issue: when I try to delete a record using the GUI the workbench get stuck, with the loading mouse indicator and I have to force quit (no visible error on log).

I will re-install workbench and see what's happens.

PS: Can you please delete on my previous comment the IP address of the server (log section)?
[27 Aug 2016 21:43] Steve Fatula
Crashes for me all the time, have to revert to old version. I'd say every other query, at least. I use SSH and private keys if t

Attachment: Workbench CrashLog.txt (text/plain), 94.61 KiB.

[7 Sep 2016 16:33] Mike H
Steve... you're crash is: https://bugs.mysql.com/bug.php?id=82409
[22 Feb 2018 0:05] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.0 release, and here's the changelog entry:

After executing a query, MySQL Workbench often quit working or exited
unexpectedly without writing to the log file. This fix improves the
overall stability of the SQL editor.

Thank you for the bug report.