@rnax Nope you didn’t miss anything. I’m sorry this happened to you (and sad this was your first experience with Obsidian) but luckily you didn’t lose anything important.
I’m not sure whether this is just a low priority for the developer or (more likely) just something that is unfixable due to a combination of being quite hard to reliably reproduce and also very likely an “upstream” bug—meaning the bug is in the Electron framework itself or in one of the modules that Obsidian uses like CodeMirror.
I agree with you that the #1 priority for a note taking “second brain” app should be making sure the stuff you type in gets saved. But Obsidian is so freaking good at everything else that even with that (scary) shortcoming, myself and others continue to accept that risk.
I sincerely hope that this bug gets fixed one day but it’s looking less and less likely as months turn into years and people continue to report this issue. Maybe it will just magically disappear one day when Electron fixes it, which seems to be what happened to the kernel panic bug that was really big a while back.
What I’ve done to protect myself is:
- set snapshot period to 1 minute
- script that makes hourly backups of my vault and preserves the last 30 days
- script to monitor my vault and pop up an alert the moment it detects an “empty” file that was created >2 min ago
Even with all of this, I still hit the bug sometimes and just deal with it. I’m still hoping one day I figure out a way to trigger it so we can at least have hope of a fix.