ghostty stays resident after a failed memory allocation but refuses to open additional windows #10566
Unanswered
JakePi3
asked this question in
Issue Triage
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
I was running opencode via ghostty with a large AI model loaded up into ollama. The model took up nearly all of my VRAM. As a result, I believe ghostty failed to allocate memory (see logs). It was left running in a zombie state but unable to allocate new windows.
Expected Behavior
Ideally process would recover once memory became available again, but since state might be non-deterministic an exit or crash would also be preferable.
Actual Behavior
Attempting to run ghostty would just result in no action.
When run from another terminal, it would give some normal startup diagnostics but no new window would open. No crash log.
It was possible to start a new window by passing
--config-default-filesas a flag.Once the original ghostty process (run with default
--gtk-single-instance=trueflag) was killed, operation returned to normal.Reproduction Steps
1 Run any process that fills up 99% of VRAM (e.g. ollama with a large enough model loaded)
2 Open Ghostty
It might be easier to just cause the allocation to fail programatically to see if this could be reproduced.
Ghostty Logs
Ghostty Version
OS Version Information
Omarchy 3.3.3 Stable
(Linux only) Display Server
Wayland
(Linux only) Desktop Environment/Window Manager
hyprland 0.53.1
Minimal Ghostty Configuration
gtk-single-instance=trueAdditional Relevant Configuration
No response
I acknowledge that:
```) on separate lines.Beta Was this translation helpful? Give feedback.
All reactions