Live-share: Cannot join Live Share session (constantly loading)

[mavaddat]

Issue Type: Bug

The extension is constantly loading, but I never join the session. The join session invitation is also received (the invitation within VS Code that pops up a notification to 'Accept'), but I cannot ever join the session.

Extension version: 1.0.1847
VS Code version: Code - Insiders 1.44.0-insider (6cf3dd97465b2f4f666b66758991d720e003b0f4, 2020-03-27T06:00:06.803Z)
OS version: Windows_NT x64 10.0.19592

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-3540M CPU @ 3.00GHz (4 x 2990)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.91GB (9.26GB free)|
|Process Argv|-n C:\Users\MavaddatJavid\AppData\Local\Temp\vsliveshare\tmp-DF206CDFD09294F9AD2D15D0C16095A87119\Visual Studio Live Share.code-workspace|
|Screen Reader|no|
|VM|0%|

[setaskin]

Hi thanks for reaching out. This is a recently discovered bug that repro on VS Code insiders. We are investigating the issue. Do you mind to try it with VS Code Stable? This should unblock you. Please let us know how goes, feel free to comment if you have further questions

[beratetik]

Hi,
I encountered this problem 3 days ago and still doesn't work.
The issue that I faced is about live-share extension. I researched it but couldn't find any issue like I was experiencing.

you can use the following information as a guide @setaskin;

Tried:

• _Signed out and signed in with github account_
• _Signed out and signed in with microsoft account_
• _Removed and re-installed live share extension_
• _Re-installed VSCode Insider_

Those things that I tried on Mac OS (Mojave 10.14.5) and Windows 10 Pro (VS Code Insider) and couldn't achieve to join.

• It works without any trouble on the online VSCode version with "Guest User".

on the Windows 10 PRO:
VS Code version: Code - Insiders 1.44.0-insider (6cf3dd97465b2f4f666b66758991d720e003b0f4, 2020-03-27T06:00:06.803Z)
OS version: Windows_NT x64 10.0.18362

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 2712)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.96GB (10.89GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

Extensions (2)

Extension|Author (truncated)|Version
---|---|---
remote-wsl|ms-|0.44.2
vsliveshare|ms-|1.0.1847

[fubaduba]

@setaskin seems like anonymous join works, but there is a problem in joining after sign in.

[setaskin]

@fubaduba nope, I have tested with with anonymous join, it still hangs. It only repro when the guest is VS Code Insiders. VS code stable works fine. Probably bug is on VS Code Side.

[mavaddat]

Hi thanks for reaching out. This is a recently discovered bug that repro on VS Code insiders. We are investigating the issue. Do you mind to try it with VS Code Stable? This should unblock you. Please let us know how goes, feel free to comment if you have further questions

Thank you for the work-around suggestion; however, I would like to only have one install of VS Code on my system at the moment. I may try with a portable "install" of the stable branch and report back.
What is interesting is that if I disable certain extensions (the ones that aren't related to Python coding) and I completely uninstall then reinstall the LiveShare extension pack, then I can get LiveShare to work in VS Code Insiders. It seems like there is an issue with the LiveShare audio extension specifically (because merely uninstalling that one can sometimes fix the problem), but I cannot pinpoint this.

My current extensions

Extension | Author (truncated) | Version
-- | -- | --
vscode-django | bat | 0.20.0
npm-intellisense | chr | 1.3.0
vscode-markdownlint | Dav | 0.34.0
vscode-eslint | dba | 2.1.1
githistory | don | 0.6.3
python-extension-pack | don | 1.6.0
prettier-vscode | esb | 3.20.0
code-runner | for | 0.9.17
beautify | Hoo | 1.5.0
vscode-peacock | joh | 3.6.0
chat | kar | 0.33.0
vscode-codemetrics | kis | 1.24.0
vscode-github | Kni | 0.30.3
MagicPython | mag | 1.1.0
vscode-azurefunctions | ms- | 0.21.0
python | ms- | 2020.3.69010
remote-wsl | ms- | 0.44.2
azure-account | ms- | 0.8.8
powershell-preview | ms- | 2020.3.1
vsliveshare | ms- | 1.0.1847
vsliveshare-audio | ms- | 0.1.80
vsliveshare-pack | ms- | 0.3.4
debugger-for-chrome | msj | 4.12.6
vscode-for-node-js-development-pack | nod | 2.0.1
java | red | 0.58.0
vscode-xml | red | 0.11.0
vscode-checkstyle | she | 1.3.2
vscodeintellicode | Vis | 1.2.6
vscode-java-debug | vsc | 0.25.1
vscode-java-dependency | vsc | 0.9.0
vscode-java-pack | vsc | 0.8.1
vscode-java-test | vsc | 0.22.2
vscode-maven | vsc | 0.21.2
jinja | who | 0.0.8
vscode-import-cost | wix | 2.12.0
vscode-preview-server | yui | 1.3.0
markdown-all-in-one | yzh | 2.7.0

[setaskin]

@mavaddat , thanks for the info, this is really helpful to investigate. I am not sure if the problem caused by Audio , because when I tested Live Share extension itself ( no audio) VS Code insiders still hangs. Still investigating the issue. We will post here when the issue is fixed. Adding @jramsay as he might have comments about the audio extension.

[jramsay]

@mavaddat, @setaskin; thanks for the info! I just tested the same scenario on VS Code Insiders and confirmed that the issue repros without the audio extension installed.

[pjninnim]

Issue appears to be resolved in the latest updates.

[jramsay]

@pjninnim: thanks for confirming the fix! I'll resolve this issue.