runtime/debug: SetGCPercent grabs heap lock on G leading to potential self-deadlock #32105
Comments
No this is different. What's happening is a self-deadlock on the G calling SetGCPercent.
SetGCPercent is just incorrect. It should only grab the heap lock on the system stack. What's surprising to me here is that this wasn't happening before. I guess calls to SetGCPercent are just rare enough that they don't trigger a morestack? |
Change https://golang.org/cl/177857 mentions this issue: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The first failure on the dashboard is
https://build.golang.org/log/b3defcc2b2f4353229022a8bc9c810b2b1f5d37e
But it might have occur before as runtime tests were failing, runtime/debug tests weren't run.
It is freezing during a copystack. Using stackDebug variable, I've this kind of trace.
@mknyszek is it related to #31966 or similar issues ?
The text was updated successfully, but these errors were encountered: