Skip to content

memory consumption eruption for large golang file #530

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

Closed
mainred opened this issue May 7, 2019 · 3 comments
Closed

memory consumption eruption for large golang file #530

mainred opened this issue May 7, 2019 · 3 comments
Labels
duplicate This issue or pull request already exists topic: memory Huge memory consumption

Comments

@mainred
Copy link

mainred commented May 7, 2019

Thank you for creating the issue!

Please include the following information:

  1. Version of golangci-lint: golangci-lint --version (or git commit if you don't use binary distribution)
    golangci-lint has version 1.15.0 built from 901cf25 on 2019-02-18T08:24:43Z
  2. Config file: cat .golangci.yml
  3. Go environment: go version && go env
    go1.10.3
  4. Verbose output of running: golangci-lint run -v

I happened to have a large golang file which is 28M, and golangci-lint is blocked in Go packages loading at mode load deps types and syntax, for this sentence did not manged to print out, and golangci-lint is killed for OOM.
I found from top command that the memory usage spikes at terribly 9G.

20514 root      20   0 10.025g 9.831g      8 S  86.7 16.0   1:22.47 golangci-l+
@mainred mainred changed the title memory consumption eruption memory consumption eruption for large golang file May 7, 2019
@alexec
Copy link
Contributor

alexec commented Jul 10, 2019

See #337

@tpounds tpounds added the topic: memory Huge memory consumption label Sep 25, 2019
@tpounds
Copy link
Contributor

tpounds commented Sep 25, 2019

Closing as duplicate of #337.

@tpounds tpounds closed this as completed Sep 25, 2019
@tpounds tpounds added the duplicate This issue or pull request already exists label Sep 25, 2019
@jirfag
Copy link
Contributor

jirfag commented Sep 27, 2019

Hi, I’m not sure it will be fixed in #337. It’s not a common use case. Why can’t you split file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists topic: memory Huge memory consumption
Projects
None yet
Development

No branches or pull requests

4 participants