Skip to content
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: acquireSudog cache seems not to be effective #9069

Closed
rsc opened this issue Nov 7, 2014 · 1 comment
Closed

runtime: acquireSudog cache seems not to be effective #9069

rsc opened this issue Nov 7, 2014 · 1 comment
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented Nov 7, 2014

This program's heap grows without bound in the Go 1.4 beta. Keith, can you take a look?

package main

import (
    "runtime"
    "sync"
)

func main() {
    runtime.GOMAXPROCS(4)

    var mu sync.Mutex
    var cond sync.Cond
    cond.L = &mu
    go func() {
        for {
            cond.Signal()
        }
    }()
    mu.Lock()
    for {
        cond.Wait()
    }
}
@rsc
Copy link
Contributor Author

rsc commented Nov 7, 2014

Comment 1:

Actually, this may just be that there are no GC points, because the allocation of the
sudog is not allowed to garbage collect. There's a real bug here somewhere but this is
not the right test program.

Status changed to Invalid.

@rsc rsc added this to the Go1.4 milestone Apr 14, 2015
@rsc rsc removed the release-go1.4 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants