-
Notifications
You must be signed in to change notification settings - Fork 646
go doc consuming CPU #2152
Comments
As far as I know, the Go extension doesn't use any tool called Can you disable all other extensions and see if you still see the issue? |
The 'doc' in Activity Monitor represents a
|
@aplsek Select the process in the Activity Monitor, and then select the "info" button on the top, that will open up a detailed view which will have the parent information. Check if the processes with the process name Another thing to try is to run |
Thanks for that @grillbiff. These are for doc processes as shown in the screenshot in We use
Lets try and disable these 2 features and see if that helps your case. For the first feature, lets use
For the second feature, if you are seeing the documentation on the side like in the below picture, press Ctrl+Space to hide it. |
Hi, I tried changing to both |
@grillbiff Also ensure that the docs side of the completions are not expanded. |
@ramya-rao-a I think it has been disabled, the documentation does not appear unless I explicitly press the small info icon |
Ah! My mistake. So, VS Code always calls The Go extension which implements this I was under the assumption that this I have pushed a fix for this. Can you try it out?
The first 3 are flags that will get passed to Remember to kill all existing processes for |
Hi, |
Thats right @grillbiff |
Hi, Is there an ETA on when the fix is going to be part of the official release? Not sure I want to install beta-version of the plugin as that would block the future updates... Thanks! |
The latest update (0.9.1) to the extension has this fix. |
I am seeing high CPU consumed by the 'doc' subprocesses. This started happening in the last two weeks after the latest release. The following 4 processes are spawned as soon as I start typing into a
.go
file, I have a single editor window opened:Visual Studio Version: 1.25.0-insider
Go plugin: 0.7.0
Is there a way howto disable go doc or howto analyze this further?
The text was updated successfully, but these errors were encountered: