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.

Sign up for GitHub

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: "sweep increased allocation count" on linux/arm64 during bootstrap #42543

Closed
bcmills opened this issue Nov 12, 2020 · 6 comments
Closed

runtime: "sweep increased allocation count" on linux/arm64 during bootstrap #42543

bcmills opened this issue Nov 12, 2020 · 6 comments
Labels
arch-arm64 compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Linux
Milestone
Go1.20

Comments

@bcmills
Copy link
Contributor

bcmills commented Nov 12, 2020

2020-11-11T20:26:44-b641f0d/linux-arm64-packet

Possibly related to #32026; see also #21729.

CC @aclements @mknyszek
@bcmills bcmills added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. arch-arm64 labels Nov 12, 2020
@bcmills bcmills added this to the Backlog milestone Nov 12, 2020
@cherrymui
Copy link
Member

Looks like the bootstrap compiler crashes? It could be due to an old bug in the bootstrap toolchain.

@bcmills bcmills changed the title runtime: "sweep increased allocation count" on linux/arm64 runtime: "sweep increased allocation count" on linux/arm64 during bootstrap Mar 30, 2022
@bcmills
Copy link
Contributor Author

bcmills commented Mar 30, 2022

greplogs --dashboard -md -l -e '# bootstrap/.*\n(.*\n)*fatal error: sweep increased allocation count' --since=2021-01-01

2022-03-20T16:05:03-6673d5d/linux-arm64-packet

@bcmills
Copy link
Contributor Author

bcmills commented Mar 30, 2022

This should be fixed by #44505, assuming that that actually happens as planned for Go 1.19.

@bcmills bcmills modified the milestones: Backlog, Go1.19 Mar 30, 2022
@ianlancetaylor
Copy link
Contributor

Rolling forward to 1.20 milestone.

@ianlancetaylor ianlancetaylor modified the milestones: Go1.19, Go1.20 Jun 24, 2022
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
@prattmic prattmic moved this to Triage Backlog in Go Compiler / Runtime Jul 25, 2022
@rsc
Copy link
Contributor

rsc commented Aug 4, 2022

Builders are now on Go 1.17. This should stop happening.

@rsc rsc mentioned this issue Aug 4, 2022
Closed
@aclements
Copy link
Member

There have been no occurrences of this since the 2022-03-02 log @bcmills linked above, and we have reason to believe this is fixed, so I'm going to close this. If it does happen again, we can reopen.

Repository owner moved this from Triage Backlog to Done in Go Compiler / Runtime Nov 8, 2022
@aclements aclements moved this to Done in Release Blockers Nov 8, 2022
@golang golang locked and limited conversation to collaborators Nov 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-arm64 compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Linux
Projects
Release Blockers
Status: Done
Milestone
Go1.20
Development

No branches or pull requests
6 participants
@rsc @aclements @ianlancetaylor @bcmills @gopherbot @cherrymui