go: cmd/compile: sporadic memory corruption on 386 (32-bit) builders

Various sweep increased allocation count errors have started cropping up in or near go/build invocations in various go commands.

2020-03-15T08:13:55-32dbccd/linux-386-clang 2020-03-14T07:03:15-d774d97/linux-386-sid 2020-03-16T20:59:27-ff1eb42/linux-386-387 2020-03-15T08:13:55-32dbccd/linux-386-clang 2020-03-14T07:03:15-d774d97/linux-386-sid 2020-03-13T20:43:12-e2a9ea0/openbsd-386-62

Since go/build is involved, this may be related to the go/types crash cluster (#37602, #37507, #37690).

CC @griesemer @matloob @aclements @danscales @mknyszek @cherrymui

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 25 (17 by maintainers)

Commits related to this issue

Most upvoted comments

I’m going to declare this fixed. The original CL with fixed rules is in, both for 386 and amd64. I’m not seeing any similar failures on the dashboard since the fixes went in.

I might have figured out what is wrong. Read the description of the CL above for all the gory details. I’m not 100% sure, but enough so to try and submit this again and see what happens (I still can’t reproduce outside trybots).