-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Significant/breaking increase in memory usage in 1.19 #731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
With some more experimentation I was able to determine the specific commit which jumped memory usage for me: This is fine (completes @
This is not (completes @
And current master (completes @
|
Same issue here, had to pin version to 1.18. |
hi, thank you, |
Hi, my project is not open source yet. Below is the config which I use from circleci:
|
Unfortunately the project I am experiencing this with is also not open-source. However, it's possibly notable that this project is "larger", containing about 200 packages plus dependencies, and we've had to manage how concurrent we allow the linker to be to control memory consumption. In this particular case, based upon the commit message and the noticeable increase in |
We (at Docker) are also interested in ways to (directly or indirectly) limit golangci-lint memory consumption; we are seeing a regression with 1.18.0 (compared to 1.17.1), I guess it's repeatable and Docker is open source; see moby/moby#39964 for more details |
ok, thank you, let's continue in #337, there are too many similar issues about memory |
Using the release binary for amd64/linux, on 1.18 my linter set completes using
2364.4MB
. On 1.19 it gets killed at 4GB by CircleCI. Running locally on OSX to experiment, it uses 8-9GB.Updating to latest
master
on OSX to get this fix: #725 has no effect (no change in memory usage at all).Note that this memory usage increase appears to be coming from
megacheck
:v1.18.0
tag:master@9d1610b
(1.19+a few more commits)The text was updated successfully, but these errors were encountered: