Errors when a workspace starts up with several remote plugins

Description

Errors when a workspace starts up with several remote plugins

Reproduction Steps

When I try to start a workspace with several remote plugins (java, go, ts, xml, yaml, node debug) I can observer several error (listed below).

OS and version:
Minikube start command: minikube start --cpus 4 --memory 10240 --docker-opt userland-proxy=false --extra-config=apiserver.authorization-mode=RBAC minikube version: v0.28.2

Diagnostics:

• all plugins have been successfully processed stream error: stream ID 1; HTTP_1_1_REQUIRED Error: Failed to run the workspace: “Plugins installation process failed. Error: Plugin broking process for workspace workspaceozixry8v80yfou5l failed with error: stream error: stream ID 1; HTTP_1_1_REQUIRED”

• Starting VS Code extensions processing zip: not a valid zip file Error: Failed to run the workspace: "Plugins installation process failed. Error: Plugin broking process for workspace workspaceozixry8v80yfou5l failed with error: zip: not a valid zip file

• write /tmp/vscode-extension-broker817819086/plugin/extension/server/org.eclipse.lsp4xml-uber.jar: cannot allocate memory Error: Failed to run the workspace: “Plugins installation process failed. Error: Plugin broking process for workspace workspaceozixry8v80yfou5l failed with error: write /tmp/vscode-extension-broker817819086/plugin/extension/server/org.eclipse.lsp4xml-uber.jar: cannot allocate memory”

• Plugin installation timeout

[garagatyi]

@l0rd @ibuziuk Should OSIO-Che team include this issue into the upcoming sprint? Seems to be important and can block languages team

[garagatyi]

Closing this issue since reproduced case is fixed. Feel free to reopen if other cases are reproduced