MySQL Bugs: #92222: Corrupt workspace content after forced program exit or hard reboot

Bug #92222	Corrupt workspace content after forced program exit or hard reboot
Submitted:	29 Aug 2018 10:41	Modified:	15 Jan 2021 14:53
Reporter:	Andi Arpo	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.21	OS:	Windows (Microsoft Windows 10 Pro)
Assigned to:		CPU Architecture:	x86
Tags:	workspace

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Screenshot of pop-up

Attachment: MySQL Workbench lost workspace.png (image/png, text), 16.66 KiB.

Workbench 8.0.13 corrupted workspace files after crash

Attachment: Workbench 8.0.13 lost workspaces after crash.png (image/png, text), 83.82 KiB.