Bug #85526 Application crashes after synchronizing model
Submitted: 17 Mar 2017 18:21 Modified: 17 Apr 2017 20:26
Reporter: Kim Vandenbroek Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.4 OS:Mac OS X (10.11.6)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[17 Mar 2017 18:21] Kim Vandenbroek
Description:
After synchronizing a revised model with a single table in a localhost database, clicking on the dialog window close button, or simply clicking on the 'Close' button after the "Synchronization Completed Successfully' message appears, will cause Workbench to crash with the log shown below.

Typically, I 'Save to File...' before clicking the 'Execute' button, but that doesn't seem to cause a crash.

 ----[For better reports, please attach the log file after submitting. You can find it in /Users/kimv/Library/Application Support/MySQL/Workbench/log/wb.log]

12:08:24 [INF][      WBContext]: Parsing application arguments.
12:08:24 [INF][      WBContext]:     /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
12:08:24 [INF][      WBContext]:     -psn_0_5866904
12:08:24 [INF][      Workbench]: Starting up Workbench
12:08:24 [INF][      Workbench]: Loading main window
12:08:24 [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/kimv/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
12:08:24 [INF][      WBContext]: WbContext::init
12:08:25 [INF][            WBA]: Looking for extension modules for WBA...
12:08:25 [INF][            WBA]: 0 extension modules found
12:08:25 [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
12:08:25 [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
12:08:25 [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
12:08:25 [WRN][            grt]: /Users/kimv/Library/Application Support/MySQL/Workbench/connections.xml:25: link '4D3BD53F-4773-4D66-91A8-D02F8606022E' <object GrtObject> key=owner could not be resolved
12:08:25 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Mac OS X version 6.3.4  revision 0 build 828 (32 bit)
	Configuration Directory: /Users/kimv/Library/Application Support/MySQL/Workbench
	Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
	Cairo Version: 1.10.2
	OS: unknown
	CPU: 4x Intel(R) Core(TM) i7 CPU       M 620  @ 2.67GHz - 8.00GiB RAM

12:08:25 [INF][   ModelContext]: Found model auto-save /Users/kimv/Library/Application Support/MySQL/Workbench/admazing_model_031717.mwbd, but it is empty. Deleting it...
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-1.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-10.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-11.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-12.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-2.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-3.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-4.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-5.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-6.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-7.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-8.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/-9.autosave
12:08:25 [INF][    WQE backend]: Found auto-save workspace /Users/kimv/Library/Application Support/MySQL/Workbench/sql_workspaces/localhost__root-1.autosave
12:10:46 [INF][      SqlEditor]: Opened connection 'localhost: root' to MySQL Community Server (GPL) version 5.7.14
12:10:47 [INF][     AutoCCache]: Initializing autocompletion cache for localhost__root
12:10:48 [ERR][ SqlEditorPanel]: Could not read file /Library/WebServer/Documents/admazing/__queries/SELECT_sum_clientcontract_items_WHERE_invoice.sql: Failed to open file '/Library/WebServer/Documents/admazing/__queries/SELECT_sum_clientcontract_items_WHERE_invoice.sql': No such file or directory

How to repeat:
See above...

Suggested fix:
Unknown
[17 Mar 2017 20:26] Miguel Solorzano
Please try version 6.3.9. Thanks.
[18 Apr 2017 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".