Skip to content

Known Issues

Kenneth L edited this page May 7, 2024 · 14 revisions

Dev-environment

  • Using Docker container in VScode can sometime lead to memory leak. This usually happens after switching the active git branch.
  • Symptoms include repeated port forwarding, as evident in the Ports tab in VScode, which can be self-triggered or triggered when launching a ROS process. Memory usage will increase exponentially in the process, eventually leading to the computer freezing completely.

Recovery

Currently, there's no known permanent fixes. The following recovery procedure is a band-aid solution that helps you resume your development progress.

  • Disconnect the remote connection to the container image on VScode, and close VScode.
  • Clean uninstall VScode:
sudo apt-get purge code
rm -r ~/.vscode/
rm -r ~/.config/Code/

Instead, if VSCode has been installed with snap, the first line becomes:

sudo snap remove code
  • Reinstall VScode (snap or apt):
sudo snap install code --classic
  • Reinstall VScode Dev-container extension
    If the issue still persists, try the following
  • After clean reinstallation of VScode, DO NOT sync to your VScode extensions and enable only Dev-container
  • After VScode has been wiped clean, flush the built container images and volumes:
sudo docker system prune -a
sudo docker volume prune -a

Then reinstall VScode, and rebuild image as normal.

See Also

https://github.com/microsoft/vscode-docker/issues/2875
https://github.com/ms-iot/vscode-ros/issues/393

Clone this wiki locally