Lingering VS code processes when restarting to update

[QwertyZW]

• VSCode Version: 1.8.0
• OS Version: Windows 10 Pro, Version 1607, OS Build: 14393.576

Encountered this when updating to version 1.8.1

Lingering VS code processes in the background block it from updating itself

The processes you see here are besides the Setup process that was somewhere up the list

I had to manually kill the 6 processes you see here before I was able to update.

[joaomoreno]

Any chance you can find out the full command line which spawned those processes?

[QwertyZW]

Does VS Code/Setup/Update keep a log anywhere by default? I'm not familiar with windows 10's system log mechanisms/if it had any

[joaomoreno]

No, but if you see them again, you can use Process Hacker to figure out each process' full command line.

[QwertyZW]

[joaomoreno]

Thanks!

[joaomoreno]

@mjbvz for TypeScript
@dbaeumer @aeschli for html/languageclient

[dbaeumer]

I think the root cause of this is the extension host not shutting down. All other processes are started from the extension host and shutdown if they are asked to do so, the stream closes they use to listen on or when the process that started them disappears.

[dbaeumer]

Adding @alexandrudima. The extension host under Windows is started in detach mode to support a proper shutdown sequence. However looking at the code I can only think about one case where the extension host wouldn't shutdown: if it is busy and can't process events. @QwertyZW in your case is the --extensionHost process consuming lots of CPU cycles?

[QwertyZW]

@dbaeumer Nope. All of them looked pretty idle to me. The only one that showed any activity was the 4th one from the top and even then it was only periodic/very occasional spikes going no higher than 5%

[QwertyZW]

The processes still linger in the background after aborting. Once I manually kill those processes I'm unable to recreate the situation again. Updating works fine afterwards.

However if I keep them running, start a new window and try to update I run into the same problem.

It might be an issue related to suspending the processes (when putting comp to sleep) but I'm not sure. The system is always running/sleeping unless I shut it down for updates

[dbaeumer]

@QwertyZW when you see it again will killing the process that has --extensionHost on the command line make all the other processes go away in a reasonable amount of time?

[QwertyZW]

Will it make all the other processes go away? in 1.9 --extensionHost seems to be one of the main process' grandchildren.

[dbaeumer]

Yes, it should make all the other processes go away

[mjbvz]

@QwertyZW Can you please try upgrading to VSCode 1.10+ to pick up TS 2.2.1. Let me know if you still see the typescriptserver process hanging around. If you do, try collecting the TSS_LOGs as documented here: #21442 (comment)

[QwertyZW]

Upgraded to 1.10 a while back without a problem @mjbvz

[QwertyZW]

Upgraded again several times from 1.10 through to 1.12.2.

I think this ticket can be closed now. Please feel free do to so if this ticket is not relevant anymore.

[alexdima]

Thank you @QwertyZW

I'll close this issue for now. We know we have a problem that sometimes the extension host process lingers around. We will try to tackle it with #26445