runtime: reportZombies throws "found pointer to free object" in sweeper

[adonovan]

#!stacks
"reportZombies:+34" && "runtime.goexit"

Issue created by stacks.

This stack Ytavxw was reported by telemetry:

• crash/crash
• runtime.throw:+9
• runtime.(*mspan).reportZombies:+34
• runtime.(*sweepLocked).sweep:+160
• runtime.sweepone:+37
• runtime.bgsweep:+28
• runtime.gcenable.gowrap1:+0
• runtime.goexit:+0

golang.org/x/tools/[email protected] go1.23.4 linux/amd64 vscode (1)

@prattmic

[adonovan]

Possibly another manifestation of #71425.

[prattmic]

I believe this could theoretically be caused by #71228.

[gabyhelp]

Related Issues

• x/tools/gopls: out-of-memory failure on Windows #71065
• runtime: fatal error: found pointer to free object #47513 (closed)
• x/tools/gopls: OOM reported by fatal in runtime.mallocgc (windows) #70445 (closed)
• runtime: marked free object in span #47415 (closed)
• runtime: sweep increased allocation count #19473 (closed)
• fatal error: found pointer to free object #68047 (closed)
• x/tools/go/ssa: TestTypeparamTest/metrics.go failures #69409 (closed)
• affected/package: found pointer to free object (go runtime) #52008 (closed)
• runtime: marked free object in span on Windows #45364 (closed)
• runtime: fatal error: sweep increased allocation count in go1.7 #16778 (closed)

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

[prattmic]

I think the right way to handle this w.r.t. stacks new reopening ability is to send a CL to bump gopls go.mod to 1.23.5 (once that is released) and then mark this with the milestone of the gopls release that contains that bump?