-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zlib error: invalid distance too far back #134429
Comments
@kkat-zero In this case, it looks like the extension host process exited after 19seconds with exit code 1, which according to nodejs means "Uncaught Fatal Exception - There was an uncaught exception, and it was not handled by a domain or an uncaughtException event handler.". Unfortunately, that exit code is not very revealing towards what could be the problem. In |
@alexdima Thank you for your reply. |
@kkat-zero Thank you for the extra information, the
It looks like there is a zlib stream decoding error in the extension host. @kkat-zero I am very interested to manage to reproduce this. In the remote machine, we pass over sockets from one process to another, and I think that something might be misbehaving in this area. What is the remote Linux distribution/version that you are connecting to? Does this reproduce when connecting to any linux machine via SSH? |
@alexdima Thank you for the quick response. -Debian (version 9.13) This target Linux machine is an embedded Linux device. (MOXA-UC2100) When connecting directly with OpenSSH, this phenomenon does not occur. |
@alexdima We will inform you of additional information. A) In rare cases, this phenomenon can be connected without error. (When retrying many times) B) This embedded device has a very small internal RAM of 256MB. When VS Code makes a remote connection, I'm checking that a memory swap is occurring because the internal RAM alone isn't enough. When I checked the memory used when the startup was successful, it was confirmed that a total of about 300MB of RAM was used. |
@kkat-zero Thank you for the extra information. Indeed, it might be a bug caused by timing that reproduces on memory limited machines that need to do swapping. Is there a way for me to try this debian distro in a VM? Could you please point me to an article or some steps to simulate this environment? |
@alexdima Thank you for the quick response. However, I think it is possible to create an environment that combines only the limited memory environment with a VM. First, build a virtual environment to install Debian OS on VMWare. Once the virtual environment can be built, set the virtual memory under that environment. There are two points of concern. One thing to worry about is whether it is possible to install a general Debian OS on a PC with limited RAM. Second, when using a VM environment, there is a high possibility that the CPU processing speed and memory access speed will be faster than the actual machine. For reference, the following sites are shown. [How to build VMware] [Virtual memory setting method] |
…e extension host process, which then asks the client to resume (#134429)
…e extension host process, which then asks the client to resume (microsoft#134429)
@alexdima Is this something we can verify? Do you have a simple setup with steps? |
Unfortunately I was only able to reproduce by making changes to the source code (e.g. to add artificial delays to the extension host startup path). |
@alexdima Thank you for corresponding to solve this issue. Thank you. |
Does this issue occur when all extensions are disabled?: Yes
This is a problem that occurs when connecting the target OS to Linux from the Windows host OS using Remote Development.
If you check the logs, the extension host will start when you make a remote connection.
However, the extension host exits immediately.
"Extension Host Process exited with code: 1, signal: null." Is displayed on the log.
I guess the extended host function is timing out because the processing speed of the target OS is slow.
I set "Remote-SSH: Connect Timeout" to 500 seconds to solve this problem, but the problem still persists.
Are there any other measures?
The text was updated successfully, but these errors were encountered: