x/tools/gopls: sustained 100% cpu use from gopls for hours after editor interactions stop #38009
What did you do?
gopls continues to use CPU for hours even while no use of vscode has continued.
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
I was not continuing to edit the particular files in question on disk in the majority of scenarios (was in other Go projects), but I may have run go builds in those other projects impacting the cache.
In regards to 3109 I am not using go-group-imports (explicitly), but will double check.