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

Jump to bottom

runtime: OS thread appears to be re-used despite never releasing runtime.LockOSThread() [1.10 backport] #28985

Closed
gopherbot opened this issue Nov 28, 2018 · 1 comment
Closed

runtime: OS thread appears to be re-used despite never releasing runtime.LockOSThread() [1.10 backport] #28985

gopherbot opened this issue Nov 28, 2018 · 1 comment
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Milestone
Go1.10.7

Comments

@gopherbot
Copy link

@ianlancetaylor requested issue #28979 to be considered for backport to the next 1.10 minor release.

@gopherbot Please open a backport issue for 1.10 and 1.11.
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Nov 28, 2018
@gopherbot gopherbot mentioned this issue Nov 28, 2018
Closed
@gopherbot gopherbot added this to the Go1.10.6 milestone Nov 28, 2018
@dmitshur dmitshur modified the milestones: Go1.10.6, Go1.10.7 Dec 13, 2018
@FiloSottile
Copy link
Contributor

This issue will be backported to 1.11, and then upgrading to 1.11 will be a valid workaround, so this is not eligible for backport to 1.10.

@golang golang locked and limited conversation to collaborators Dec 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Projects
None yet
Milestone
Go1.10.7
Development

No branches or pull requests
3 participants
@FiloSottile @dmitshur @gopherbot