Bug #77324 Crash on save
Submitted: 11 Jun 2015 21:04 Modified: 11 Jul 2015 22:29
Reporter: remy jacquin Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.3.3 OS:Windows (Microsoft Windows 8.1 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[11 Jun 2015 21:04] remy jacquin 
Description:
Since I upgraded my RAM from 8Go to 16Go, I can't save my model (model that worked normaly before) : MySQL WB crash.
My logs on crash : 

22:59:42 [WRN][            grt]: C:\Users\Rémy\AppData\Roaming\MySQL\Workbench/schema.mwbd/document.mwb.xml:8213: link 'com.mysql.rdbms.mysql.datatype.curve' <object > key= could not be resolved
22:59:42 [WRN][            grt]: C:\Users\Rémy\AppData\Roaming\MySQL\Workbench/schema.mwbd/document.mwb.xml: skipping element 'link' in unserialized document, line 8213Found OpenGL version for this view: 4.3.0 - Build 10.18.14.4099
22:59:43 [INF][ Canvas backend]: Found OpenGL version for this view: 4.3.0 - Build 10.18.14.4099
22:59:44 [INF][ Canvas backend]: Found OpenGL version for this view: 4.3.0 - Build 10.18.14.4099
22:59:44 [INF][ Canvas backend]: Found OpenGL version for this view: 4.3.0 - Build 10.18.14.4099
22:59:44 [INF][ Canvas backend]: Found OpenGL version for this view: 4.3.0 - Build 10.18.14.4099
22:59:44 [INF][ Canvas backend]: Found OpenGL version for this view: 4.3.0 - Build 10.18.14.4099
22:59:45 [ERR][ Canvas backend]: OpenGL error: invalid enum
22:59:45 [ERR][ Canvas backend]: OpenGL error: invalid enum
22:59:45 [ERR][ Canvas backend]: OpenGL error: invalid enum

How to repeat:
Seriously, I don't know : this bug is appeared since I upgraded my RAM.
[11 Jun 2015 21:08] remy jacquin 
PS : My model work normally on linux MySQL WB (open, save, ...)
[11 Jun 2015 22:29] MySQL Verification Team 
Probably duplicate of bug http://bugs.mysql.com/bug.php?id=74231 and others the path has accented word letter \Rémy. Try to save in folder with path without accented letter. Thanks.
[12 Jul 2015 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".