Skip to content

runtime: sysmon-triggered garbage collection is STW #10261

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

Closed
aclements opened this issue Mar 26, 2015 · 1 comment
Closed

runtime: sysmon-triggered garbage collection is STW #10261

aclements opened this issue Mar 26, 2015 · 1 comment
Milestone

Comments

@aclements
Copy link
Member

sysmon triggers a GC if there haven't been any GCs for the last two minutes. This happens through forcegchelper, which calls startGC(gcForceMode). gcForceMode performs a STW garbage collection, but this periodic GC should be concurrent.

This is the only use of gcForceMode, which suggests that this probably arose in some transformation and the consequences of this were simply overlooked.

The fix may be as simple as calling startGC(gcBackgroundMode) and getting rid of gcForceMode.

@RLH @rsc

@mikioh mikioh changed the title sysmon-triggered garbage collection is STW runtime: sysmon-triggered garbage collection is STW Mar 27, 2015
@bradfitz bradfitz added this to the Go1.5 milestone Mar 27, 2015
@gopherbot
Copy link
Contributor

CL https://golang.org/cl/11955 mentions this issue.

@golang golang locked and limited conversation to collaborators Jul 11, 2016
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

3 participants