Maybe an infinite loop occurs during gc? #35302
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
sorry, I didn't try to reproduce it with the latest release
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I compiled an executable file and executed it.But looks like that it didn't enter the main function.And I checked the CPU usage of this process with command "pidstat -P", I found that one thread of the process occupied 100% of the CPU in user space. So I tried to debug it with gdb.
The call stack I saw is as follows:
I made a breakpoint at runtime.pidleget (),and saw that it always enter this method.It looks like a infiniteloop.It always can get idle p when call runtime.pidleget ().Then I printed the runtime.sched to see why an infinite loop occurs.
The pidle pointer looks like a circular linked list,the npidle has been reduced to a reversal.
I don't think this should ever happen.In this case .It will circulate infinitely and never end.
Can anyone help me?
3ks
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: