You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of Go are you using (go version)?
go version go1.6 linux/amd64
What operating system and processor architecture are you using (go env)?
linux/amd64
The closure passed to gopark by gcBgMarkWorker is heap allocated even though it captures no variables. In fact, the constructed closure contains only the code pointer, which is never supposed to happen. This is particularly bad since it's causing an unexpected allocation inside the garbage collector itself. Also strange is that this is an implicit allocation in the runtime, which is supposed to be disallowed.
This happens on master with SSA as well (not too surprising; it's probably a frontend issue).
FWIW, this may not need to be Go 1.6.1. We thought this was involved in oversweeping, but it appears not to be. It was just standing nearby at the wrong time.
go version
)?go version go1.6 linux/amd64
go env
)?linux/amd64
The closure passed to gopark by gcBgMarkWorker is heap allocated even though it captures no variables. In fact, the constructed closure contains only the code pointer, which is never supposed to happen. This is particularly bad since it's causing an unexpected allocation inside the garbage collector itself. Also strange is that this is an implicit allocation in the runtime, which is supposed to be disallowed.
This happens on master with SSA as well (not too surprising; it's probably a frontend issue).
/cc @RLH @rsc
The text was updated successfully, but these errors were encountered: