x/tools/gopls: high cpu when call go mod tidy

[WAY29]

Go version

go version go1.22.8 windows/amd64

Output of go env in your module/workspace:

set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\user\AppData\Local\go-build
set GOENV=C:\Users\user\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\user\coding\golang\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\user\coding\golang
set GOPRIVATE=
set GOPROXY=https://goproxy.cn
set GOROOT=C:\Users\user\.version-fox\cache\golang\current
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Users\user\.version-fox\cache\golang\current\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.22.8
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Users\user\coding\golang\src\yaklang\go.mod
set GOWORK=C:\Users\user\coding\golang\src\yaklang\go.work
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\user\AppData\Local\Temp\go-build78613495=/tmp/go-build -gno-record-gcc-switches

What did you do?

When I plan to write code normally and use some libraries from the current file, gopls will automatically import the library for me, which will cause the CPU to soar, causing the entire gopls to be temporarily paralyzed (highlighting, completion, prompts)

What did you see happen?

Sudden CPU surge
go mod tidy -modfile=C:\Users\lang\AppData\Local\Temp\gopls-tempmod246022334\go.mod

What did you expect to see?

gopls running normally

[gabyhelp]

Related Issues

• x/tools/gopls: high cpu usage all the time #70172
• x/tools/gopls: windows cpu use 100% #66945 (closed)
• x/tools/gopls: massive cpu and memory usage #46897 (closed)
• x/tools/gopls: go list causes 100% CPU load #39116 (closed)
• x/tools/go/packages: high CPU usage while processing cgo file #32821
• x/tools/gopls: high cpu usage when make changes in package which have some cgo package dependents #50151
• x/tools/gopls: autocomplete - unstoppable import #54296 (closed)
• x/tools/gopls: "stuck" at 100% CPU #34569 (closed)
• x/tools/gopls: uses too much memory (60G) #37790 (closed)
• x/tools/gopls: excessive invocations of "go mod tidy" #38816 (closed)

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

[WAY29]

xtra information:
a new computer purchased a day ago
CPU: AMD Ryzen Al 9 HX 370

[WAY29]

I found that go list also cause the CPU to soar..

[findleyr]

Thank you. This is almost certainly related to go list: when you add an import we run go list to list package information.

Does this occur for even a small module? If so, then it may indicate some real bug in go list (for example, mismatching paths that cause spurious cache misses).

[WAY29]

Thank you. This is almost certainly related to go list: when you add an import we run go list to list package information.

Does this occur for even a small module? If so, then it may indicate some real bug in go list (for example, mismatching paths that cause spurious cache misses).

Without further testing, I have moved to WSL to work on it, and while there is no evidence, I suspect Windows Defender is involved

[findleyr]

Thanks, that sounds likely if it works well in WSL. Please comment if I am misunderstanding.