Bug #80796 Data keeps being corrupted - Error unserializing GRT data
Submitted: 19 Mar 2016 7:44 Modified: 5 Aug 2016 1:22
Reporter: Nathan Carter Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.6 OS:Windows (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[19 Mar 2016 7:44] Nathan Carter
Description:
After making a number of modifications to an ERD model, I will receive an error when trying to open it that there was an error unserializing GRT data - string too long.

This happens in multiple files, only after they have been opened, modified and saved a number of times.

----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Nathan Carter\AppData\Roaming\MySQL\Workbench\log\wb.log]

How to repeat:
1. Create ERD model
2. Close MySQL Workbench
3. Open ERD Model
4. Make changes to ERD Model
5. Save ERD Model
6. Close MySQL Workbench
7. Repeat steps 3 through 6 until error occurs
[19 Mar 2016 7:45] Nathan Carter
Log file

Attachment: wb.log (application/octet-stream, text), 78 bytes.

[19 Mar 2016 17:16] MySQL Verification Team
Thank you for the bug report. Are you able to provide a model project file that presents this issue?. Thanks.

PS

Bug already reported and close in older version.

https://bugs.mysql.com/bug.php?id=60706
[23 Mar 2016 14:30] Gildonei Junior
It was working fine before update

Attachment: sample.mwb (application/octet-stream, text), 391.03 KiB.

[23 Mar 2016 14:30] Gildonei Junior
I am facing the same problem.

I had some models working fine, I formated and did a fresh install of SO and Programs and models didn't open anymore.

Workbench version 6.3.6 CE
SO Version Win 10 Pro x64 (fully updated)
[11 Apr 2016 8:30] Nathan Carter
Corrupted file

Attachment: containerERD.mwb (application/octet-stream, text), 34.97 KiB.

[5 Aug 2016 1:22] MySQL Verification Team
Thank you for the feedback. I couldn't repeat with 6.3.7.
[17 Aug 2016 8:55] Alvin Gounder
My computer is running fully update Windows 8.1 with Trend Anti-virus.
If it matters, h/w is FX8350, 16GB RAM, SSD system drive, hdd data drive.

I am using Workbench 6.3.7 community edition.

Scenario: 
I have just created an mwb file and closed the tab by clicking the x button.
Double-click the file which in file explorer to reopen.
Error Unserializing GRT data message pops up.

Quick fix (for me) is to close workbench, wait a few seconds and than double-click the mwb file again.
This always opens the file without any error.

I think it would be hard to replicate because it is not the mwb file that is actually corrupt.
Anyone else opening the file by double-clicking on it will most likely be successful in opening it.
IMO, it is the actions that the user takes prior to trying to open the file that is causing workbench to not be able to load the file.
[21 May 2017 12:25] Reginald Lather
I have just upgraded to workbench 6.3.9 community in the hope of getting rid of this annoying bug but its still there (Running window 7 64bit). After running some queries via workbench I try and open the MWB and get the 'error unserializing data string too long'. I also notice that it I close the error message and try to open again, Workbench is under the impression that its already open! giving me the 'Opening another model will close the currently open model. Do you wish to proceed opening it?
If I than navigate to the actual file location and double click - mysql workbench reverts to the  default screen.