We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@ianlancetaylor requested issue #38023 to be considered for backport to the next 1.14 minor release.
@gopherbot Please open backport issue for 1.14. This problem can cause Go programs to hang in some circumstances, with no workaround.
@gopherbot Please open backport issue for 1.14.
This problem can cause Go programs to hang in some circumstances, with no workaround.
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/225277 mentions this issue: [release-branch.go1.14] runtime: don't call wakeNetPoller during timerModifying
[release-branch.go1.14] runtime: don't call wakeNetPoller during timerModifying
Sorry, something went wrong.
This problem can cause Go programs to hang in some circumstances, with no workaround, as discussed #38023 and #38072. Cherry pick approved.
Closed by merging ca153f4 to release-branch.go1.14.
[release-branch.go1.14] runtime: don't call wakeNetPoller during time…
ca153f4
…rModifying Reduce the length of time that other timer functions can see timerModifying. In particular avoid system calls. For #38023 Fixes #38051 Change-Id: I1b61229c668e6085d9ee6dca9488a90055386c36 Reviewed-on: https://go-review.googlesource.com/c/go/+/224902 Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Michael Knyszek <[email protected]> (cherry picked from commit 355f53f) Reviewed-on: https://go-review.googlesource.com/c/go/+/225277
No branches or pull requests
@ianlancetaylor requested issue #38023 to be considered for backport to the next 1.14 minor release.
The text was updated successfully, but these errors were encountered: