x/tools/gopls: spurious SEGV in Promise

[adonovan]

#!stacks
"sigpanic" && "memoize.(*Promise).run.func2.1:+7"

Issue created by stacks.

Almost certainly more memory corruption.

This stack MTg0Ug was reported by telemetry:

• crash/crash
• runtime.gopanic:+69
• runtime.panicmem:=262
• runtime.sigpanic:+19
• golang.org/x/tools/internal/memoize.(*Promise).run.func2.1:+7
• runtime/trace.WithRegion:+19
• golang.org/x/tools/internal/memoize.(*Promise).run.func2:+1
• runtime.goexit:+0

golang.org/x/tools/gopls@v0.18.1 go1.24.3 linux/amd64 vscode (1)

[gabyhelp]

Related Issues

• x/tools/gopls: SEGV updating non-nil map in analysis.Validate #73437
• x/tools/gopls: SEGV while clearing memory in newobject #71561
• x/tools/gopls: nil deref in x/telemetry/internal/counter.(*Counter).add #73890
• gopls: automated issue report (crash) #63702 (closed)
• x/tools/gopls/test: flakes due to analyzer panics #56035 (closed)
• x/tools/gopls: automated issue report (crash) #44353 (closed)
• x/tools/gopls: SIGSEGV in cache.missingModuleError #42349 (closed)
• x/tools/gopls: SEGV accessing map[string]... #73387
• x/tools/gopls: SEGV in gcimporter.iexportCommon (bad SP) #72135
• x/tools/gopls: out-of-memory failure on Windows #71065

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}