Skip to content

Commit 27b65b4

Browse files
committed
gopls/doc: add memory usage info to troubleshooting guide
This way, we can close the memory usage tracking issue. Fixes golang/go#36943 Change-Id: I1933c103443797cb80dec3fa54fc3ddf281cf832 Reviewed-on: https://go-review.googlesource.com/c/tools/+/253577 Reviewed-by: Heschi Kreinick <[email protected]>
1 parent 77fbfae commit 27b65b4

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

gopls/doc/troubleshooting.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
# Troubleshooting
22

3-
If you see a gopls error or crash, or gopls just stops working, please follow the troubleshooting steps below.
3+
If you suspect that `gopls` is crashing or not working correctly, please follow the [troubleshooting steps](#steps) below.
4+
5+
If `gopls` is using too much memory, please follow the steps under [Memory usage](#memory-usage).
46

57
## Steps
68

@@ -17,6 +19,7 @@ describe more basic and optional trouble shooting steps
1719
## File an issue
1820

1921
You can use:
22+
2023
* Your editor's bug submission integration (if available). For instance, `:GoReportGitHubIssue` in [`vim-go`](vim.md#vim-go).
2124
* `gopls bug` on the command line.
2225
* The [Go issue tracker](https://github.com/golang/go/issues/new?title=x%2Ftools%2Fgopls%3A%20%3Cfill%20this%20in%3E).
@@ -68,3 +71,15 @@ If you are unsure of how to pass a flag to `gopls` through your editor, please s
6871
### Restart your editor
6972

7073
Once you have filed an issue, you can then try to restart your `gopls` instance by restarting your editor. In many cases, this will correct the problem. In VSCode, the easiest way to restart the language server is by opening the command palette (Ctrl + Shift + P) and selecting `"Go: Restart Language Server"`. You can also reload the VSCode instance by selecting `"Developer: Reload Window"`.
74+
75+
## Memory usage
76+
77+
`gopls` automatically writes out memory debug information when your usage
78+
exceeds 1GB. This information can be found in your temporary directory with
79+
names like `gopls.1234-5GiB-withnames.zip`. On Windows, your temporary
80+
directory will be located at `%TMP%`, and on Unixes, it will be `$TMPDIR`,
81+
which is usually `/tmp`. Please create a
82+
[new issue](https://github.com/golang/go/issues/new?title=x%2Ftools%2Fgopls%3A%20%3Cfill%20this%20in%3E)
83+
with your editor settings and memory debug information attached. If you are
84+
uncomfortable sharing the package names of your code, you can share the
85+
`-nonames` zip instead.

0 commit comments

Comments
 (0)