[Remote-SSH] Selecting a (large?) zip file in the file explorer hangs the remote VSCode server

[timothyfroehlich]

• VSCode Version: 1.55.0-insider and 1.54.3
• Local OS Version: Windows 10 Pro Version 10.0.19043 Build 19043
• Remote OS Version: Ubuntu 20.10
• Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. Open a folder that contains a very large zip file (I have one that's 753MB)
2. Click on the file in the Explorer.
3. VSCode will open a preview tab in the code editor with the little blue progress indicator line moving under the tab header. After about 30 seconds or so VSCode will begin restarting the remote connection. It'll find the server and attempt to connect, but about 30 seconds later a new connection attempt will start. Example install terminal output:

Looking for server with pid: 2936530
Found running server...

*
* Reminder: You may only use this software with Visual Studio family products, 
* as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
*

Checking server status on port 40593 with wget
380c4a50c49a: start
SSH_AUTH_SOCK====
webUiAccessToken====
listeningOn==40593==
osReleaseId==ubuntu==
arch==x86_64==
tmpDir==/run/user/1000==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime====
connectionToken==b5227e7b-e8fb-47ab-9bde-78d0c4d6c58f==
380c4a50c49a: end

Output from the Remote-SSH extension (This loops): https://pastebin.com/EHZSWAEs

This will continue until I run Remote-SSH: Kill VS Code Server on Host, which will allow me to restart the connection.
Other VSCode Remote SSH sessions on the same host don't seem to be affected.

I have seen that if I open a smaller zip file that it will hang for a few seconds and eventually return with a message like "This is a binary file, can't preview".

I got the same results with a fresh Insiders install with no other extensions.

Does this issue occur when you try this locally?: No, it instantly displays "The file is not displayed in the editor because it is too large"
Does this issue occur when you try this locally and all extensions are disabled?: N/A

Incidentally, is there a filter I can set somewhere to get vscode to not try to open the file?

[bamurtaugh]

I believe the issue with large files sounds like #1257.

[tanhakabir]

Closing as a duplicate of #1257