runtime: scavenger freezes up in Go 1.14 in Windows due to coarse time granularity [1.14 backport]

[gopherbot]

@networkimprov requested issue #38617 to be considered for backport to the next 1.14 minor release.

@gopherbot please backport to 1.14; this is a regression.

[dmitshur]

@mknyszek noted in #38617 (comment) that there is a workaround available:

So, this is a real bug. I'm not sure what the fix is, and it may be worth back-porting to 1.14? There is a workaround, which is to call debug.FreeOSMemory occasionally.

It's not a great experience, but it is worth considering.

/cc @mknyszek @aclements Now that a fix is available, do you have thoughts on how safe it would be to backport this to 1.14?

[aclements]

It's a pretty simple fix. It seems worth back-porting to me. @mknyszek ?

[mknyszek]

Backporting is fine with me, the change is not very risky.

[gopherbot]

Change https://golang.org/cl/232743 mentions this issue: [release-branch.go1.14] runtime: make the scavenger's pacing logic more defensive

[dmitshur]

Approved per discussion in a release meeting. This is a regression affecting a first class port, the workaround isn't very accessible, and the fix is not high-risk.

[gopherbot]

Closed by merging b7eca1c to release-branch.go1.14.