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

Hold on with upgrading to Go 1.14 #20734

Closed
karalabe opened this issue Mar 2, 2020 · 0 comments · Fixed by #20913
Closed

Hold on with upgrading to Go 1.14 #20734

karalabe opened this issue Mar 2, 2020 · 0 comments · Fixed by #20913

Comments

@karalabe
Copy link
Member

karalabe commented Mar 2, 2020

This is just a tracker issue to point people to if someone opens a PR to update to Go 1.14. Currently we're blocked by two issues:

  • On some systems, building the docker images blows up: runtime: mlock of signal stack failed: 12 golang/go#37436, which lends to belief that not just Go, but anything built with it might blow up too. A lot of other projects are holding off from upgrading, so probably it's sane for us to do so too.
  • The GC triggers were modified in Go 1.14, which means that the same GOGC configurations as we've had previously will consume more memory. runtime: high memory usage on Go 1.14 golang/go#37525 This might need some investigation, just chalking it up here as a potential OOM issue if we upgrade blindly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant