I happen to have a Windows computer that crashes (shows the blue screen and reboots) about once per day on average. Since most computers don’t do this and the bug I’m reporting depends on that, I expect this bug report will be low priority and may never be fixed.
Steps to reproduce
- Edit a file with Obsidian.
- For the bug to be reproduced, the computer needs to happen to crash within a few seconds of editing a file in Obsidian.
- Reboot and open Obsidian.
- See that the file that was being edited now appears to have nothing but tons of small squares in it. Text editors without rendering reveal that the file has just a bunch of zeros in columns like an empty binary file. See screenshots below.
The file’s contents are lost, but this isn’t too big of a deal since I can then just use the “File recovery” core plugin to restore the file.
Did you follow the troubleshooting guide? [Y/N]
Yes.
Expected result
The file contents should still be there. Maybe the last few seconds of changes would be lost, but everything else should remain. I don’t see this bug with any other editor; I have seen many other editors not clear files when the computer crashes.
Actual result
The file’s contents were cleared and replaced by tons of zeros.
Environment
SYSTEM INFO:
Obsidian version: v1.6.7
Installer version: v1.5.3
Operating system: Windows 10 Home 10.0.22631
Login status: not logged in
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 1
Restricted mode: off
Plugins installed: 1
Plugins enabled: 0
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Additional information
The environment information above may be incorrect. It says Windows 10 but I’m using Windows 11.
