While a can consistently cause Obsidian to crash and take Windows with it I can’t seem to find an exact reproducible pattern. I seems to happen most often when I am switching between a file in file explorer that has a lot of images in it. After a while, images will stop displaying and the explorer will stop switching between two files. At this point the system stops responding. Close Obsidian. The Obsidian process is still running and the system doesn’t respond until the process dies (manual termination doesn’t work) or the system is restarted.
Also see video below.
Obsidian doesn’t crash and does not make Windows stop responding.
Features in Obsidian stop working (outline, explorer, opening files) and then after Obsidian is closed the process will not terminate and the Windows system becomes unresponsive.
Operating system: Windows 10 Pro
Obsidian version: v0.13.19
Installer version: v0.12.19
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: on
Base theme: dark
Community theme: none
Snippets enabled: 0
Safe mode: on
The only plugins I have turned on are Outline and Tags.
In task manager I notice an orphaned Obsidian process and some Microsoft Edge WebView2 processes (not sure if related, does Electron use WebView2?). The Obsidian process will not terminate from Task Manager.
Something else that is odd is that the CPU utilization is low (9%). Is Electron firing system interrupts? or is something happening at the Kernel level to interfere with scheduling? Idk, just noting that it is odd from a typical process crash.