Yes.
Silently crashed after every startup.
When running the app on cmd, the error message is
[49444:0724/153000.494:FATAL:content\browser\gpu\gpu_data_manager_impl_private.cc:415] GPU process isn’t usable. Goodbye.
Cannot use debug information.
Uninstalling Obsidian and downloading the latest version didn’t solve the issue.
Refer to Electron GitHub Issue, this seems to be related to gpu-sandbox and the SID, which is a Windows ACL element.
In my case, the day the issue occurred was the exact same day I installed Antigravity.
opened 02:52PM - 24 May 26 UTC
platform/windows
crash
bug
has-repro-comment
42-x-y
### Preflight Checklist
- [x] I have read the [Contributing Guidelines](https:/… /github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.
### Electron Version
42.2.0, 37.6.0
### What operating system(s) are you using?
Windows
### Operating System Version
Windows 11 25H2
### What arch are you using?
x64
### Last Known Working Electron version
_No response_
### Does the issue also appear in Chromium / Google Chrome?
I don't know how to test
### Expected Behavior
Electron applications should launch normally even if the directory contains unparseable or orphaned zombie SIDs, or gracefully handle the permission validation error without crashing the entire GPU process.
### Actual Behavior
The GPU process crashes on startup with exit_code=-2147483645 and outputs "FATAL:gpu_data_manager_impl_private.cc: GPU process isn't usable. Goodbye."
### Testcase Gist URL
_No response_
### Additional Information
**TL;DR:** Electron apps crash with exit_code=-2147483645 because the folder's DACL contains orphaned zombie SIDs (S-1-15...). Granting permissions to `S-1-15-2-2` (ALL RESTRICTED APPLICATION PACKAGES) or running `icacls /reset` fixes the crash. This is closely related to the LPAC sandbox requirement discussed in #49143.
#### Description
Recently, on my Windows PC, many Electron-based desktop applications (such as Discord, Bitwarden, LM Studio, Postman, VS Code, etc.) crash frequently, making them completely unusable. The error messages are as follows:
```
[33240:0524/193721.652:ERROR:content\browser\gpu\gpu_process_host.cc:999] GPU process exited unexpectedly: exit_code=-2147483645
[33240:0524/193721.652:FATAL:content\browser\gpu\gpu_data_manager_impl_private.cc:417] GPU process isn't usable. Goodbye.
```
After searching online, I found that other users have reported the same error recently:
- liliMozi/openhanako#1083
- anthropics/claude-code#61372
- postmanlabs/postman-app-support#14149
Currently, the only temporary solution is to add the `--disable-gpu-sandbox` parameter at startup. However, this requires doing it manually every time and is not a permanent solution.
#### Hypothesis
After repeated troubleshooting and verification with AI, we ruled out hardware and driver issues. (During this time, I tried reinstalling drivers, reinstalling software, reinstalling Windows, adjusting Core Isolation and HAGS, updating BIOS, etc., but nothing worked.)
Finally, the AI identified the possible cause: an issue with the security permission list (DACL) of the application folder, which contains an unresolvable "zombie SID" (shown as "Unknown Account" in the Windows interface). This conclusion can be consistently reproduced using the following steps.
#### Reproduction Steps
Please create a clean Electron project then package, or use an existing Electron application folder directly (the following example uses VS Code with PowerShell):
1. Add a zombie SID to the application folder:
```PowerShell
icacls "$env:LOCALAPPDATA\Programs\Microsoft VS Code" /grant "*S-1-15-2-999-999-999:(OI)(CI)(F)"
```
2. Run the application:
```PowerShell
& "$env:LOCALAPPDATA\Programs\Microsoft VS Code\Code.exe" --verbose
```
**Expected Result**: The application will crash immediately during GPU initialization and output the following error logs:
```
[37568:0524/201836.841:ERROR:content\browser\gpu\gpu_process_host.cc:999] GPU process exited unexpectedly: exit_code=-2147483645
[37568:0524/201836.841:FATAL:content\browser\gpu\gpu_data_manager_impl_private.cc:415] GPU process isn't usable. Goodbye.
```
3. Run the following command to reset permissions and remove the zombie SID. After that, the application will work normally again:
```PowerShell
icacls "$env:LOCALAPPDATA\Programs\Microsoft VS Code" /reset
```
#### Additional Context
Before submitting this issue, I researched related past reports and noticed:
* #49143
It mentions that enabling the network sandbox in newer versions might cause permission issues, requiring the following command to grant permissions:
```PowerShell
icacls <install dir> /grant *S-1-15-2-2:(OI)(CI)(RX)
```
Following this clue, I did a cross-test and made a new discovery: if both the unknown zombie SID and the `S-1-15-2-2` permission exist at the same time, the application can start successfully without crashing.
Since I’m not familiar with programming and this is an issue originating from Electron, I am writing this post simply to share the issue itself and how they resolved it.
As another issue mentioned, it was easily resolved by using the --disable-gpu-sandbox option. ( Obsidian on Windows 11 keeps crashing without error messages (Solved) )
But I think this is a temporary solution.
On the Electron GitHub issue, they suggest restore SID permissions to the application folder.
Since this involves modifying ACL permissions, I can’t say anything for certain and just want to offer a general direction:
Check if an unknown account SID (starting with S-1-15-2-...) is inherited under Folder Properties > Security tab in the Obsidian installation path, and try to remove it by tracing back to the parent folder it’s inherited from.
Grant permissions using PowerShell (though I’m not sure what specific permissions these are).
Finally, I can run the app without --disable-gpu-sandbox option.
Thanks for brining this weird bug to our attention.
This is an upstream electron problem, so we’ll wait for upstream fix.electron issue for workarounds .