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
syscall: Windows WriteConsole syscall hangs indefinitely #34929
Comments
Can you provide whole part of stacktrace? Can you reproduce always? |
I have never been able to reproduce it. Here is more of the stack trace, but I don't imagine it can possibly help you any further.
|
I think I've just come across the answer to this question. It seems that Powershell basically pauses if you click around and is woken up by pressing enter. It must not just be the rendering that's paused, but the actual output too. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I'm not sure. I'm having a hard time reproducing the error from the very same binary...
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Attempted to print something to the console, running an application in PowerShell.
After nothing happened for a while, I used "ctrl+c" to try and kill the process. This program has signal handlers to gracefully handle SIGINT. The program responded instantly to the SIGINT, and happily printed some log lines to the console during this logic.
What did you expect to see?
My logs, printed to the console without issue, in a timely manner.
What did you see instead?
I cannot say for sure if the SIGINT somehow un-froze the logic or if the frozen thread stayed frozen forever. However, my program coincidentally happens to include logic designed to detect potential deadlocks. After the SIGINT this detection logic printed stack traces of goroutines that hadn't returned in a timely manner.
Here is part of the stack trace that I believe is relevant:
I do not know what could cause this syscall to stall for 5 minutes. I find it hard to believe that it has anything to do with Go, but I haven't had any success searching for an answer in the Windows syscall man pages.
The text was updated successfully, but these errors were encountered: