-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deadlock when resizing on Windows #3277
Comments
Can you get me the stack traces of all threads? Its very likely this is possible on other platforms too just not happening for whatever reason and I'd like to look into it. |
Sure, here is the full callstack of main thread
|
Sorry I meant all threads. Can you get me the stacks of all threads? I want to see what the rest are doing. |
Ah my bad, here are the callstacks |
After reading deeper into the source, I found the It also lead to a crash that, after resizing, left click the area newlly created, the app crashed for Debug build at
Also I believe that's why there is nothing show from cmd.exe in the terminal window It blocks on, and there is nothing show in ghostty window
|
I’m not entirely sure if this is the right place to ask, but I’m wondering how to get Ghostty on Windows. I couldn’t find any information about it in the documentation or on the download page. Could someone point me in the right direction? |
just build from source with zig 0.13, either natively on windows or cross build from linux |
@gaocegege The github readme in the Roadmap says Windows support is not yet done |
Yes, if this is a Windows-only issue I will close it. But if this deadlock can potentially impact other platforms I need to look into it. That's why I've kept this open until that's verified. |
We were using `opts.backend` for which `initTerminal` was not called. This lead to the PTY being created with a size of (0, 0), making the `CreatePseudoConsole` to fail, then making the IO thread to exit early. This was the cause of the hang observed in ghostty-org#3277.
When resizing on windows, the ghostty window is likely to stuck.
The stacktrace shows that it's waiting forever on BlockingQueue in MainThread, with the mutex held in
push
, which means it's impossible to notify the queue withpop
.Also the
pop
method is designed to be called on MainThread :(It's not reproducible on linux as the breakpoint set on the highlighed line never hits.
Workaround:
Instead of waiting forever, a finite wait works for me
The text was updated successfully, but these errors were encountered: