runtime: invalid pointer found on stack regression in Go1.15 triggered by mapassign in init #41816
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes (this is the latest release).
What operating system and processor architecture are you using (
go env
)?docker pull golang:1.15
(as of Oct 6, 2020).go env
OutputWhat did you do?
Run
go test
on the same code that had been working from 1.10 through 1.14.The
<scrubbed>:91
line in the stack trace refers to a map assignment within an init function. The map is declared in the global scope, and is a map of string keys to large (several hundred byte) struct values. The map was initialized at declaration time usingmake
without an explicit capacity hint.What did you expect to see?
no panic/throw.
What did you see instead?
Repeatable, but not deterministic (happens 33% of the time) failures of the form:
The text was updated successfully, but these errors were encountered: