Observed behavior
Cant reopen my library
Expected behavior
open my existing library
Steps required to reproduce
My computer crashed with Aspect opened.
Operating system/Hardware used
Windows 11, Ryzen 5 CPU, Nvidia GPU
I’ve implemented some robustness improvements to better cope with possibly corrupted revisions:
- Revisions are now written in a way that makes impossible to have data corruption in case of application crashes - system crashes can still be an issue, though, although also less likely
- Invalid/corrupted revisions will simply be skipped during library load so that the library can be successfully loaded anyway
- If possible, missing/corrupted revisions will be restored from other library instances
The case that cannot currently be recovered automatically is when there are multiple library instances and one of the instances has changes that have not been synchronized and the corresponding revision(s) are corrupted/missing (internal ticket: #1577).
The improvements above will be in the next release (which is imminent). If they don’t fix the issue and if you don’t have the library shared across multiple devices, you can also delete the .revs folder within the library folder to make the library load again.