live-share

live-share copied to clipboard

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.

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

@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.

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

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 [email protected] 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 https://github.com/MicrosoftDocs/live-share/issues/355#issuecomment-388918515, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVIcbeAN6gWFK_rbZOmTwiVeVOb8deVks5tyc5BgaJpZM4T6cpU .

-- Jason

Same here

Thanks for reporting, working on fixing this.

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

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

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!

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.

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!

@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.

@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.

February 2019 and still have this issue. Any solution?

February 2019 and still have this issue. Any solution?

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

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

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.

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

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

Same here when I start live share with latest VS Code

This is happening to me, this issue should be reopened

This continues to happen on the latest version of Live Share on Windows as well. The VS Code window is idle and untouched, but CPU usage bounces between 30-100% of a CPU core.

Version: 1.45.0-insider (user setup)
Commit: ece7aaee861d7261a728d52ce436c667030ce17d
Date: 2020-05-01T09:46:47.589Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Bump!

My vsls-agent was stuck ripping 3Mbit/sec write to disk, continuously (for over an hour) after all users had left my session.

Frustrating, what on earth would cause such a thing? I'm running Ubuntu 20.04.

I had to put 'er down - once I turned off the live-share session, the vsls-agent remained running but the disk usage fell off, so that's good.

Reactivating the issue. Since we started to get user reports about it again. cc: @BrunoGuardia

Bump on this Vsls agent using 100% CPU and slowing everything to a crawl. MacOS latest.

@cvaldez98 - Carlos, can you indicate your VSCode and LiveShare versions too? And it would be useful to look at your logs, check if you can use the "Live Share : Export Logs" commands, to see if there is more data on why this is happening.

Working on a repro for this one.

@BrunoGuardia Happy to help! VSCode Version: 1.47.3 Livesharedocs.zip

Ran into this today and had to kill vsls-agent manually. CPU was pegged at 100%

Version: 1.47.3 Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e Date: 2020-07-23T13:08:29.692Z Electron: 7.3.2 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Darwin x64 19.5.0

Live share version 1.0.2619

livesharelogs.zip

Fyi I suspect my issue was related to https://github.com/MicrosoftDocs/live-share/issues/3612, I have not observed this problem since that was fixed.

Seeing the same thing today on the latest version of the extension