Live-share: [VS Code] Agent terminated with exit code: 2 and signal null

Created on 26 Apr 2018  路  13Comments  路  Source: MicrosoftDocs/live-share

Product and Version [VS/VSCode]: VS Code 1.22.2
OS Version [macOS/Windows]: macOS 10.13.4
Live Share Extension Version: 0.2.487

Steps to Reproduce / Scenario:

  1. Tried joining a session and Agent terminated with exit code: 2 and signal null popped up
  2. Every time I relaunch VSCode same errors pops up

I already tried uninstalling and deleting the folder from ~/.vscode/extension. After reinstalling the same error pops up after "Signing in" shows up in the menu bar of VSCode.

I already deleted all the Keychain Items of vs-live-share, but also without luck...

Logs:
live-share.zip

acquisition and activation bug vscode

Most helpful comment

Until a fix is released, this workaround should resolve the issue:

mkdir -p ~/.local/share

Then restart VS Code.

All 13 comments

@belazer Thanks for reporting this - sorry you're hitting an issue here! Also, big high five for including your logs. 馃檶 That's super useful!

It looks like this is a new problem from what I see. Is that right? 0.2.405 started okay, but 0.2.487 is failing?

Are you seeing any errors in Help > Toggle Developer Tools?

Hey @Chuxel! Thanks for getting back to me! 馃檪

Yeah the previous versions were starting properly.

The Dev Tools are showing the same error quite a few times:
bildschirmfoto 2018-04-26 um 16 51 14

@belazer Hmmm... something is up here. @avanderhoorn is going to take a look.

@belazer, can you try running the following command from a console:

/Users/fabian/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.487/dotnet_modules/vsls-agent

If it starts successfully, the last message will say Listening on pipe "VSLS" (and then you can hit Ctrl+C to kill it). But based on the exit code 2 you reported, I think it will fail to start and print some exception message, that may give some clue to the problem.

@jasongin This is the output:

[Agent I] vsls-agent v0.2.487.7570 (pid: 16469)
[Agent I] Reminder: You may only use this software with Visual Studio and Visual Studio Code, as described in the license (https://go.microsoft.com/fwlink/?linkid=872556).
[Agent I] Start time: 2018-04-26 17:50:01.702
[Agent I] Using VSLS service: https://insiders.liveshare.vsengsaas.visualstudio.com/
[Agent I] VSLSAgent/0.2.487.7570 VSLS/2.2 PlatformName/Darwin 17.5.0 PlatformVersion/17.5.0.0
[Agent I]
[Agent I] Proxy settings from env variable: http_proxy was null and https_proxy was null
[Agent I] (1001) Listening on pipe "VSLS"

So looks like this works 馃

Thanks...
Anyway, just now we were able to reproduce the problem internally and we're investigating...

@belazer This appears to be happening enough we're going to likely spin a release. Thanks so much for rasing it! Stay tuned...

Good to know @Chuxel! Thanks for the fast responses 馃檶

I'm having the same issue, here's the log output I'm getting: (if it's helpful). I LOVE the feature! so anything I can do to get it back online.

dev-tools-console-output.log

@derekclair So glad you like Live Share and sorry you're hitting issues! Good news is we have reproduced it and are working on getting a fix out ASAP.

Until a fix is released, this workaround should resolve the issue:

mkdir -p ~/.local/share

Then restart VS Code.

I opened https://github.com/dotnet/corefx/issues/29354 to track the underlying issue in .NET Core.

We'll add a workaround to Live Share.

We just released v0.2.489 that should solve this problem for good! Sorry about the issue!

Was this page helpful?
0 / 5 - 0 ratings