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
runtime: mcentral.freeSpan bug for empty? #34316
Comments
It seems that you are just asking a question, not reporting a bug. We don't use the issue tracker for discussions (see https://golang.org/wiki/Questions). This particular topic should be discussed on golang-dev@googlegroups.com. Thanks. I believe the answer to this question is that the code is preserving invariants for the concurrent garbage collector. |
I think this is a bug, but nfreed stops the bug effect.@ianlancetaylor |
OK, if you think there is a bug, I will reopen it, but you need to provide much more explanation as to what you think the bug might be. |
thinks.@ianlancetaylor |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Why would we remove mspan from empty to nonempty in mcentral if there is no free object in mspan?
Fortunately, nfreed is 0 when wasempty is 1 which make
mheap_.central[spc].mcentral.freeSpan
does not work, but still I think it is a bug for mcentral.freeSpanI think it should be :
The text was updated successfully, but these errors were encountered: