golangci-lint will be stuck and use huge memory in go 1.20 environment, both mac and linux.

[chenyahui]

Welcome

• Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, etc.).
• Yes, I've tried with the standalone linter if available (e.g., gocritic, go vet, etc.). (https://golangci-lint.run/usage/linters/)

Description of the problem

golangci-lint will be stuck and use huge memory in go 1.20 environment, both mac and linux.

Rollback the go version to go1.19, and golangci-lint returns to normal.

mac

linux

Version of golangci-lint

$ golangci-lint --version
# Paste output here

golangci-lint has version v1.50.1 built from (unknown, mod sum: "h1:C829clMcZXEORakZlwpk7M4iDw2XiwxxKaG504SZ9zY=") on (unknown)

Configuration file

$ cat .golangci.yml
# paste output here

Go environment

$ go version && go env
# paste output here

Linux: go version go1.20 linux/amd64

Verbose output of running

$ golangci-lint cache clean
$ golangci-lint run -v
# paste output here

$ golangci-lint run
WARN [runner] The linter 'deadcode' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter. Replaced by unused.
WARN [runner] The linter 'structcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter. Replaced by unused.
WARN [runner] The linter 'varcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter. Replaced by unused.
[1] 2629 killed golangci-lint run

Code example or link to a public repository

// add your code here

[boring-cyborg]

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

[vitaly-eureka-security]

I can confirm this happens on Windows as well

[csabaujvari]

I can confirm also. I'm using OSX

[ldez]

duplicate of #3535,#3533,#3470