Obsidian crashing and refusing to close itself, it is already terminated?

Once you’ve done the above, delete everything above this line.

Steps to reproduce

This is a lot. Cause or error partially unknown, behavior known.

  1. Start to create a new vault, give it a name.
  2. Look up the folder location and, dunno if relevant pick a location inside an empty Google drive folder.
  3. Confirm the location then tab out and wait/do other things (unsure what caused it).
  4. If it says “not responding” in the header when tabbing back in but showing the window contents the bug starts to appear.
  5. You will want to try to close it. Click the X button. It won’t close. Also, make sure you use Administrator on all attempts to kill it.
  6. Next, you will try to close it via task bar. It will turn gray. Not closing.
  7. Now if you try closing it via X again it will say the process is stuck so you press on “End process”. Even this will not close it.
  8. You can continue to try taskkill in CMD, it will say “Success, the task to terminate has been sent to the process”, but the process is still open,
  9. followed by the attempt to “End Process” in Task manager. Will not work.
  10. You can now try Windows Resourcemonitor. If you try to kill the task there, it will prompt “Access denied”. Why that is, it will not tell you.
  11. I also tried Microsoft Process Explorer which also was just saying Access Denied in any way I tried
  12. If that all fails, there is a software I tried to use because forums said it might do something. That software is called System Informer. When trying to kill the process via System Informer it says (roughly translated from my error message, see screenshots below) “Unable to terminate Obsidian.exe (PID 10588) It has been attempted to access a process which has been terminated.” Which is logically impossible, a process which has been terminated can’t exist to be still attempted to be accessed. Somewhere in the program stopping to respond it bricked itself so strongly that it won’t even close on runtime.
  13. I even tried logging to another admin account on my Windows machine to kill it from there, to no avail. The only options left that I see are
  14. a) log out of all windows users and log back in which sometimes helps,
  15. b) restart the entire machine to remove the process from the list.

I can’t do that before writing this bug report so I will have to add to this post after I sent it and tried all options I can think of.

Did you follow the troubleshooting guide? [Y/N]

As far as I understand yes, my Obsidian is pretty basic and I don't recall changing much settings. I recently installed it and it used to work fine until recently.

Expected result

I expect 4. to not happen and if it does still happen, that 5. makes the program just close and the situation to be "solved".

Actual result

The program is stuck, gray, not responding, access denied, can't kill process ID 10588, nothing is working to unbrick it on runtime.

Environment

Can't access the command palette because the program is stuck. I will add screenshots.

Additional information

Obsidian (not responding, pressing on end process does nothing)


Obsidian after pressing “End process”, notice no “x” symbol

Some info from Microsoft Process Explorer
grafik
Obsidian DLLs and Files

Task Manager - no response, Obsidian, no response, task details in resourcemonitor, process explorer

Error message in System Informer grafik

Video contains me clicking on kill process on Obsidian and shows how it doesn’t close. Link can embedd in Discord, can’t embedd elswhere sadly.
https://cdn.discordapp.com/attachments/548947129880805397/1317033805386743828/Obsidian_bug_2024-12-13_07-32-41.mp4?ex=675d36d0&is=675be550&hm=fc41d65eb7d3ebdf0092bc34f386eb6a3c83c11776e86e2b4da954584d208c13&
Alternative link for the video

Logging out the Windows user works to terminate the process, you don’t have to restart the whole device, at least. Not much more though.

I never had a problem killing Obsidian. I have the feeling that this was caused by Obsidian getting hang on google drive. Please review the the troubleshooting guide and make sure that Gdrive is configured to keep the file local.