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: cannot ReadMemStats during GC #19812

Open
aclements opened this Issue Mar 31, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@aclements
Member

aclements commented Mar 31, 2017

GC holds the worldsema across the entire garbage collection, which means nothing else can stop the world, even during concurrent marking. Anything that does try to stop the world will block until GC is done. Probably the most interesting such operation is ReadMemStats.

We should fix GC to only hold worldsema during sweep termination and mark termination. The trickiest part of this is probably dealing with GOMAXPROCS changing during GC, which will affect mark worker scheduling.

/cc @RLH

@aclements aclements added this to the Go1.9Maybe milestone Mar 31, 2017

@aclements aclements modified the milestones: Go1.10, Go1.9Maybe Jun 21, 2017

@aclements aclements modified the milestones: Go1.10, Go1.11 Nov 8, 2017

@bradfitz bradfitz modified the milestones: Go1.11, Go1.12 May 18, 2018

@ianlancetaylor ianlancetaylor added this to the Go1.12 milestone May 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment