``` #!stacks "sigpanic" && "golang.org/x/telemetry/internal/counter.(*Counter).add:=274" ``` Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks). I suspect this is another case of gopls heap corruption, but haven't investigate yet. This stack `wbY-eA` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2025-05-24.json): - `crash/crash` - [`runtime.throw:+9`](https://cs.opensource.google/go/go/+/go1.24.3:src/runtime/panic.go;l=1101) - [`runtime.sigpanic:+16`](https://cs.opensource.google/go/go/+/go1.24.3:src/runtime/signal_unix.go;l=922) - [`sync/atomic.(*Uint64).CompareAndSwap:=179`](https://cs.opensource.google/go/go/+/go1.24.3:src/sync/atomic/type.go;l=179) - `golang.org/x/telemetry/internal/counter.(*Counter).add:=274` - [`golang.org/x/telemetry/internal/counter.(*Counter).Add:+26`](https://cs.opensource.google/go/x/telemetry/+/v0.0.0-20241220003058-cc96b6e0d3d9:internal/counter/counter.go;l=176) - [`golang.org/x/telemetry/internal/counter.(*Counter).Inc:+1`](https://cs.opensource.google/go/x/telemetry/+/v0.0.0-20241220003058-cc96b6e0d3d9:internal/counter/counter.go;l=146) - [`golang.org/x/tools/gopls/internal/server.(*server).Hover.StartLatencyTimer.func3:+13`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:gopls/internal/telemetry/latency.go;l=99) - [`golang.org/x/tools/gopls/internal/server.(*server).Hover.func1:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:gopls/internal/server/hover.go;l=25) - [`runtime.deferreturn:+10`](https://cs.opensource.google/go/go/+/go1.24.3:src/runtime/panic.go;l=610) - [`golang.org/x/tools/gopls/internal/server.(*server).Hover:+30`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:gopls/internal/server/hover.go;l=52) - [`golang.org/x/tools/gopls/internal/protocol.serverDispatch:+335`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:gopls/internal/protocol/tsserver.go;l=505) - [`golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.ServerHandler.func3:+5`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:gopls/internal/protocol/protocol.go;l=160) - [`golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.handshaker.func4:+52`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:gopls/internal/lsprpc/lsprpc.go;l=509) - [`golang.org/x/tools/gopls/internal/protocol.Handlers.MustReplyHandler.func1:+2`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:internal/jsonrpc2/handler.go;l=35) - [`golang.org/x/tools/gopls/internal/protocol.Handlers.AsyncHandler.func2.2:+3`](https://cs.opensource.google/go/x/tools/+/gopls/v0.18.1:internal/jsonrpc2/handler.go;l=104) - `runtime.goexit:+0` ``` golang.org/x/tools/gopls@v0.18.1 go1.24.3 linux/amd64 vscode (1) ```
Issue created by stacks.
I suspect this is another case of gopls heap corruption, but haven't investigate yet.
This stack
wbY-eAwas reported by telemetry:crash/crashruntime.throw:+9runtime.sigpanic:+16sync/atomic.(*Uint64).CompareAndSwap:=179golang.org/x/telemetry/internal/counter.(*Counter).add:=274golang.org/x/telemetry/internal/counter.(*Counter).Add:+26golang.org/x/telemetry/internal/counter.(*Counter).Inc:+1golang.org/x/tools/gopls/internal/server.(*server).Hover.StartLatencyTimer.func3:+13golang.org/x/tools/gopls/internal/server.(*server).Hover.func1:+1runtime.deferreturn:+10golang.org/x/tools/gopls/internal/server.(*server).Hover:+30golang.org/x/tools/gopls/internal/protocol.serverDispatch:+335golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.ServerHandler.func3:+5golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.handshaker.func4:+52golang.org/x/tools/gopls/internal/protocol.Handlers.MustReplyHandler.func1:+2golang.org/x/tools/gopls/internal/protocol.Handlers.AsyncHandler.func2.2:+3runtime.goexit:+0