-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
x/tools/gopls: memory usage #43968
Comments
please follow the steps in https://github.com/golang/tools/blob/gopls/v0.6.4/gopls/doc/troubleshooting.md#debug-memory-usage to include the relevant information when filing issues about gopls |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
/cc @heschik |
You seem to have a number of particularly expensive packages, notably golang.org/x/text, open in your workspace. Have you opened your entire GOPATH as your workspace folder? That will definitely lead to very high memory usage. We'd like to be more efficient, but for now you will be much better off opening just the project you're working on. |
Hi @heschik, I just have one project and all the packages that I have installed is what i'm using. |
Please make sure that the folder you've opened as your workspace folder in VSCode contains only code you've written. If you still see high memory usage, please upload a gopls log following https://github.com/golang/vscode-go/blob/master/docs/troubleshooting.md#collect-gopls-information? |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
just save a change on my project
What did you expect to see?
Better improvement of the memory
What did you see instead?
here you have the img:
https://ibb.co/94kgRXy
The text was updated successfully, but these errors were encountered: