vsls-agent consuming 100% cpu

[jtokoph]

vslslogs.zip

Product and Version [VS/VSCode]: VSCode 1.23.0
OS Version [macOS/Windows]: OSX 10.13.4
Live Share Extension Version: 0.3.98
Target Platform or Language [e.g. Node.js]: Ruby?

Steps to Reproduce / Scenario:

After "a while", and potentially only after waking my mac from sleep/lock, the vsls-agent process starts to consume 100% cpu.

Unfortunately I don't know the steps to reproduce, but it has happened multiple times. I'm opening the issue because I wasn't able to find anyone else reporting an issue via google/gh searches. Hopefully someone will also search and add their experience here.

I think it might be related to the computer locking/sleeping, but haven't been able to reproduce consistently. When I see the cpu usage goes to 100% I reload vscode and it all goes back to normal.

I should note that this is happening while signed into live share but I do not have an active sharing session. As far as I'm concerned the extension should be considered idle. I do usually have a debug process going within vscode for a rails server. Not sure yet if that is required for this issue to happen.

Feel free to close due to needing more info, but I thought it would be valuable to have a place for others to report if they have this issue.

[lindskogen]

+1, same problem here - my battery was just drained in 2h from full charge and found the same thing that you did!

[Chuxel]

@jtokoph (and @lindskogen) Thanks for reporting this. We'll need to see if we can repro this one but clearly this should not be happening.

[Platzii]

Same problem, currently I have no clue what triggers this behaviour. I also have no active shared sessions when this occurs.

Product and Version [VS/VSCode]: VSCode 1.23.1
OS Version [macOS/Windows]: macOS 10.12.6
Live Share Extension Version: 0.3.98
Target Platform or Language [e.g. Node.js]: Go

[jtokoph]

I’ve had to completely disable the extension to avoid overheating/fan burnout/battery drain. So unfortunately I won’t be able to provide any further information. I was able to repro once by putting my machine to sleep for 5 minutes and waking it to 100% cpu. Tried 5 more times and it didn’t happen. So very hit or miss if that’s the cause.

On Mon, May 14, 2018 at 11:34 Simon Lepla ***@***.***> wrote: Same problem, currently I have no clue what triggers this behaviour. I also have no active shared sessions when this occurs. *Product and Version* [VS/VSCode]: VSCode 1.23.1 *OS Version* [macOS/Windows]: macOS 10.12.6 *Live Share Extension Version*: 0.3.98 *Target Platform or Language* [e.g. Node.js]: Go — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#355 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVIcbeAN6gWFK_rbZOmTwiVeVOb8deVks5tyc5BgaJpZM4T6cpU> .

-- Jason

[hsorbo]

Same here

[Priya91]

Thanks for reporting, working on fixing this.

[RicoLaaa]

I have the same issue, with liveshare extension installed, while not even being logged to liveshare.

[seangates]

After disabling, I now can use my computer again ...

[lostintangent]

As an update for everyone: we've got a fix for this issue and are just finalizing some validation. We're hoping to release the fix early next week, and we'll update this bug with progress. Thanks for the patience!

[gevorggalstyan]

Important notes:

1. vsls-agent stays on and is using CPU even when VS Code is completely turned off (Quit on mac).
2. Sometimes there are more than one vsls-agent active processes running.

[lostintangent]

This issue has been resolved with the 0.3.198 release that went out this afternoon. If folks could update to that, and let us know if they're still experiencing issues, that would be great. Thanks again for reporting this!

[gerhardcit]

@gevorggalstyan , just updated Code Insider to
dbd7f09189947497c77755d0738c115d689c680

It seems the reduced to one agent only across all the instances opened, but it still runs high on CPU.

[gevorggalstyan]

@gerhardcit I am using VS Code Version 1.23.1 (1.23.1) d0182c3417d225529c6d5ad24b7572815d0de9ac (The blue one, not the insider), and VSLS version is 0.3.198.

I did not notice any issues with CPU consumption a few days already.

Hope the versions info helps you to solve the issue.

[voxsoftware]

February 2019 and still have this issue. Any solution?

[guangqianpeng]

February 2019 and still have this issue. Any solution?

March 2019 and still have this issue. Any solution:(

[kevinmanify]

Same here. Issue still exists.
VS Version 1.31.1 (1.31.1)
After disabling LiveShare, VS seems normal again.

[anibalsanchez]

I can confirm a similar issue. In my case, running Ubuntu 18 and VS Code 1.32.1.

When I open multiple instances of VS Code, and work for several hours. At some point, vsls-agent goes crazy and puts the CPU at 200%. If I don't stop the process asap, there is no alternative than power off to restart everything.

Uninstalling LiveShare solved the issue. Weirdly, I can't remember when I installed it.

[andreixk]

This issue is still happening. I uninstalled LiveShare, but the process is STILL running! i restarted VS code, the process is still there. only killing the process manually removes it

[Sandstedt]

Still happening for me to on a MacBook Pro (Retina, 15", late 2013) on Catalina v10.15.3 using latest VS Code:

Version: 1.43.0
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-09T19:34:44.548Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

[Moulick]

Yep, happening as of today as well

[setaskin]

@BrunoGuardia since this issue previously assigned to you. Is there any investigation findings? . We started to get recent reports that users experience it again. cc: @fubaduba @Davsterl for info.

[BrunoGuardia]

no investigation results that I remember, other than the observation the agent was logging a lot of data

[gyula-s]

And this is today.
Version: 1.53.2 Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4 Date: 2021-02-11T11:45:54.515Z Electron: 11.2.1 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Darwin x64 20.3.0

[Mellbourn]

Y'all lucky. For me it is very common that vsls-agent is way above 100%. Right now it is above 500%.

[kgrandly]

Same problem... ☹️

[toridoriv]

500% today.

Version: 1.57.0-insider (Universal)
Commit: 1e446dfadf588ec28b3fdba7ac083bfa1d45df3c
Date: 2021-06-01T05:12:30.409Z
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin x64 20.5.0
Extension version: v1.0.4360

[Davsterl]

@toridoriv Do you mind sending attaching / sending logs?

[toridoriv]

@toridoriv Do you mind sending attaching / sending logs?

No problem! I have one from May 28th and the one from today. Let me know if I can be of any help.
vsls-agent_2021-05-28-230449_Mackenzie.wakeups_resource.txt
vsls-agent_2021-06-01-183135_Mackenzie.wakeups_resource.txt

[pmirandaarias]

Same problem here...

[patheticGeek]

This thing is hungrier than a newborn baby! And there is only one person connected.

[fattslug]

I've been having battery issues with my MacBook Pro 16" for the past few days. I would have it plugged in and it would be actively draining battery at a pretty fast rate. My fan was going off the wall trying to cool the laptop.

I just went to Activity Monitor to see wtf is going on and found vsls-agent consuming 199% CPU.
I closed the process and lo and behold my Macbook start charging up, my fan slows down and shuts off, and everything is back to normal.

I feel like my laptop was trying to fight off covid for the last few days and I just cured it.

It should be noted, there was no LiveShare session active. Before I closed the process, I double-checked to make sure. So not sure why it was even running.

[aaroncraigongithub]

I'm seeing vsls-agent at 100% and fan running high on my macbook. I did a LiveShare session earlier today using VSCode Insiders. Now, even with VSCode shut down I'm seeing the high CPU usage.

[danielcaldas]

Same issue here, draining battery quite quickly

[ramithuh]

vscode wasn't even running, have the same issue

[gabriellet]

Also having this issue on a 2019 MacBook Pro and it's causing the fan to run constantly. It's got a 2.4 GHz 8-Core Intel Core i9 and 16 GB of memory, so I found this really surprising. I'm on VSCode v1.61.2 and LiveShare v1.0.5065. I was not actively using LiveShare when this was happening.

Sample of vsls-agent.txt

Let me know if there's any additional information I can provide that might help track down this issue.

[Fail-Safe]

I experience this issue with vsls-agent as well. The trigger I have found is when VSCode is open and my internet connection drops (or I reset it intentionally). I can trigger this 100% CPU issue reliably by rebooting my router while my MacBook is locked (but turned on) and VSCode is left running.

[MrkTheCoder]

Processor: Intel i7 7700
OS: Windows 10 64bit v1607 Build 14393.2906
RAM: 32GB
Storage: SSD
VS Code: v1.64.2
Live Share: v1.0.5330

I have the same problem with "Live Share" in VS Code! Even some of my friends with the same version of VS code/Live Share but newer Windows 10 versions have the same problem. If "Live Share" be Enabled and even we do not use it, When we start VS Code, CPU usage will go so high in our systems, and processor Fan gets crazy. Image of Taskbar:

The whole Command-Line of VS Code process:

I had this problem 6 months ago! while trying to test it, but back then I disable it since I didn't need it. But now I need to use Live Share in a remote development!

Any idea how to solve this problem!?

BTW, I can join others with VS Code app in Windows easily!

[MrkTheCoder]

After my last post and on the next day, Without do any changes, VSCode started to behave normally without using any abnormal CPU usage! Even while Live Share was active!! (Sorry I forget to report that!)

But! Today I notice some of the VSCode plugins got updated and the problem with Live Share was raised again!! Live Share is still in the same version "v1.0.5330". and I leave the VSCode window open and after 10 min of high CPU usage, it gets back to normal again!

[backbone87]

I recently started to see that as soon as i started a live share session the CPU would go up to 100% and continuously was consuming more memory. On a fresh checkout of our project this didnt happen and it also didnt happen for other repos like rxjs.
Once i installed dependencies (yarn 3.2 monorepo) in the fresh checkout it started happening there again. In my original project copy i then started to incrementally remove all node_modules folders and could see memory growth stopping as soon as only 1 node_modules was left. At that point CPU consumption was still 100%. After also removing the last node_modules folder live share started behaving normally.

After further investigation I noticed some odd symbolic links in the node_module folders to their own package. This behavior was added to yarn in v3 (we recently switched to yarn 3, that is why i didnt have this problem before). It can be disabled in the .yarnrc.yml with nmSelfReferences: false.

ref: yarnpkg/berry#3206
ref: yarnpkg/berry#3256
ref: yarnpkg/berry#3332

I dont know, if this is the root cause (recursive symbolic links) for this particular issue since it only happens once you start a live share session while most of the problem descriptions in this issue do not mention explicitly when live share begins to take 100% CPU.

TLDR: watch out for recursive symbolic links, live share cant handle them

[derekbekoe]

We’ve made improvements in this area since this issue was filed (i.e. the vsls-agent process and associated dependencies have been removed). We believe this may have improved your experience and are closing this issue. If this issue still persists for you, please comment on the issue and let us know. Thank you.