Bug #109500 When we lose power and workbench crashes, sql_workspace autosave are bad
Submitted: 29 Dec 2022 19:58 Modified: 30 Dec 2022 10:36
Reporter: Paul Coene Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.26 OS:Windows (Microsoft Windows 7 Home Premium Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[29 Dec 2022 19:58] Paul Coene
If I am running workbench with multiple workspaces open and I lose power, the next time I open a workspace for which workbench has an autosave file, I get a restore file corrupt error.

I've lost power 4 times on 2 machines in the last 18 days and every single time those workspaces are claimed to be corrupt and I am forced to ignore to continue and I lose all my workspace information.

I have since been make my own backups of my workspaces, but that seems to be doing what your code is already trying to do, preserve my work.

How to repeat:
Open a db and open several tabs of work with various queries.  Drop power suddenly to windows PC running workbench (db for me is remote).

Suggested fix:
Make autosave files that work.
[30 Dec 2022 10:36] MySQL Verification Team
Hello Paul,

Thank you for the bug report.
Imho this is duplicate of Bug #76534, please see Bug #76534.

Ashwini Patil