You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As go has release go1.20, there is some memory leak bugs in go lint tool golangci-lint when using go1.20, and the problem has been fixed in golangci-lint v1.51.0). (Related issues: golangci/golangci-lint#3565). But the defaultVersion of golangci-lint in vscode-go is still v1.50.1, so when using vscode-go extension with go1.20, and choose linter as golangci-lint, the memery consumed by golangci-lint will be horrible.
Steps to reproduce the behavior:
Upgrade go version to 1.20
set "go.lintTool": "golangci-lint"in vscode settings
edit some go code
wait for the memory consumed by golangci-lint slowly grows
Screenshots or recordings
The text was updated successfully, but these errors were encountered:
LAShZ
changed the title
outdated golangci-lint defaultVersion version causes memory leak
outdated golangci-lint defaultVersio causes memory leak
Feb 9, 2023
What version of Go, VS Code & VS Code Go extension are you using?
Version Information
go version
to get version of Go from the VS Code integrated terminal.gopls -v version
to get version of Gopls from the VS Code integrated terminal.code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.Go: Locate Configured Go Tools
command.go version go1.20 darwin/arm64
Share the Go related settings you have added/edited
Describe the bug
As go has release go1.20, there is some memory leak bugs in go lint tool
golangci-lint
when using go1.20, and the problem has been fixed in golangci-lint v1.51.0). (Related issues: golangci/golangci-lint#3565). But the defaultVersion of golangci-lint in vscode-go is still v1.50.1, so when using vscode-go extension with go1.20, and choose linter as golangci-lint, the memery consumed by golangci-lint will be horrible.Steps to reproduce the behavior:
"go.lintTool": "golangci-lint"
in vscode settingsScreenshots or recordings
The text was updated successfully, but these errors were encountered: