You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is connecting to a persistent docker container I manually started, and then attaching to the container via the remote explorer. I am working inside this container for a lengthy period of time, which is started with CMD like:
Over time, the number of defunct processes grows within the container. When I attempt to reconnect to the container, there is a significant bottleneck in the following steps:
[23089 ms] Start: Run in container: for pid in `cd /proc && ls -d [0-9]*`; do { echo $pid ; readlink /proc/$pid/cwd || echo ; readlink /proc/$pid/ns/mnt || echo ; cat /proc/$pid/stat | tr "
[23864 ms]
[23864 ms]
[26440 ms] userEnvProbe PATHs:
...
...
[279891 ms] Start: Run in container: for pid in `cd /proc && ls -d [0-9]*`; do { echo $pid ; readlink /proc/$pid/cwd || echo ; readlink /proc/$pid/ns/mnt || echo ; cat /proc/$pid/stat | tr "
...
...
[532731 ms] Start: Run in container: mkdir -p '/tmp/devcontainers-xxxxxx' && cat > '/tmp/devcontainers-devcontainers-xxxxxx/env-loginInteractiveShell.json' << 'envJSON'
...
Only workaround I have found is to restart the container, which cleans up all of the zombie processes. Then connecting to the container is fast again.
The text was updated successfully, but these errors were encountered:
This is connecting to a persistent docker container I manually started, and then attaching to the container via the remote explorer. I am working inside this container for a lengthy period of time, which is started with CMD like:
Over time, the number of defunct processes grows within the container. When I attempt to reconnect to the container, there is a significant bottleneck in the following steps:
Only workaround I have found is to restart the container, which cleans up all of the zombie processes. Then connecting to the container is fast again.
The text was updated successfully, but these errors were encountered: