-
Notifications
You must be signed in to change notification settings - Fork 18k
Huge number of SIGURG eating up the CPU #68462
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
Comments
Related Issues and Documentation
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
see #37942, I don't see anything about CPU time here |
@seankhliao Please do not close the issue without any confirmation. If you need proof of something, ask and wait at least for some time and then close it. Anyway, here is your proof: cut.mp4 |
as indicated by the other issue, sigurg is used by the runtime internally for preemption, if your application is stuck it is unlikely to be the cause, only a symptom. |
Go version
go version go1.21.6 linux/amd64
Output of
go env
in your module/workspace:What did you do?
strace the thread with high CPU usage
same program in #68414, but closed without any further response.
What did you see happen?
What did you expect to see?
less signals wasting CPU time?
The text was updated successfully, but these errors were encountered: