Desktop, Windows, v1.12.4: Closing one of two open vaults closes both

Bug reports
1

Ever since v1.12.4 on Windows, Obsidian suddenly closes both open vaults / windows when trying to close one of them.

Steps to reproduce

  • Create two vaults.
  • Have both open at the same time in two windows.
  • Close one of the windows.
  • Obsidian first hangs for a moment, then both windows close.

Did you follow the troubleshooting guide?

No, not yet.

Expected result

  • One should be able to close one of the windows / vaults without the other getting closed too.
  • When opening Obisdian from the taskbar, only one vault (the last one that was open) should open. Instead both windows / vaults that was closed due to this bug opens.

Actual result

  • Both windows / vaults close when I close one of them.
  • Both windows / vaults open again when I open Obsidian.

Environment

  • Windows 11 25H2, x64
  • Obsidian v1.12.4
1 Like
2

How can I provide logs? Through a plugin?

Edit: Logstravaganza did not catch it. It is set to log all (debug).

| Timestamp | Originator | Level | Message |
| --------- | ---------- | ----- | ------- |
| 2026-02-27T19:18:21.183Z | plugin:logstravaganza | info | \[Logstravaganza] Proxy set up (v2.3.0) |
| 2026-02-27T19:18:45.391Z | plugin:logstravaganza | info | \[Logstravaganza] Proxy set up (v2.3.0) |
| 2026-02-27T19:21:58.984Z | plugin:logstravaganza | info | \[Logstravaganza] Proxy set up (v2.3.0) |
3

I’m experiencing this as well. There’s also a ~6-second delay when closing the application.

1 Like
4

I can’t reproduce.

Please, follow the Troubleshooting Guide and report back.

5

I started follow Troubleshooting Guide.

I opened a sandboxed vault. Now I have three windows that open and closes each time I close one of them. :sweat_smile:

6

A change in this update is that windows are grouped on the Windows taskbar.

I tried closing windows from there, instead of the big X top right. That worked.

7

did you download and reinstall Obsidian?

8

The delay I mentioned before also doesn’t occur when I close the application via the taskbar thumbnail preview.

This is a fresh installation.

9

Ok, I can reproduce.

10

As a workaround, go Setting->Appearance->Window Frame Style->Select Native restart Obsidian.

We will investigate this problem.

3 Likes
11

Description: The application is experiencing consistent full-system crashes rather than simple window management issues. Even actions that seem like “slow closing” are actually the entire process terminating unexpectedly.

Steps to Reproduce:

  1. Creating a New Vault: Every time I attempt to create a new vault, the application crashes immediately (though the vault folder is successfully created on the disk).

  2. Closing a Vault Window: When multiple vaults are open, closing one window causes the entire application to crash/exit.

  3. Exiting the App: The application often hangs or crashes during a standard exit.

Error Logs (from Windows Event Viewer): I am seeing two consistent error codes during these crashes:

  • Exception Code: 0xc0000005 (Access Violation)

  • Exception Code: 0xc000041d (An unhandled exception was encountered during a user callback)

  • Faulting Module: Obsidian.exe (Version: 1.12.4.0)

Observed Behavior: It appears there might be an internal conflict regarding memory allocation or process management, leading to these “Access Violation” errors. I have already tried running sfc /scannow (which repaired some system files, but did not fix the Obsidian crash), disabling hardware acceleration, and clearing the %AppData% cache, but the issue persists.

Request: I hope the team can look into these specific memory-related exception codes. I am happy to provide any additional logs, system information, or screen recordings to help resolve this.

12

We figured that this was caused by an upstream electron bug.

We rebuilt 1.12.4 for windows with an older Electron version that doesn’t have this bug.

For anyone affected, just download and reinstall obsidian from the website.

3 Likes
13

You should’ve bumped the version number for this one. Both for visibility (hey, we fixed a bug), and because replacing an existing release messes up package managers like Scoop and WinGet: Same version now gets a hash mismatch.

https://github.com/ScoopInstaller/Extras/issues/17307