ros2cli: NodeStrategy init Hanging

https://github.com/ros2/ros2cli/blob/094bcd9d8ba0a381f3598eeaba03eb45ed3d2df1/ros2cli/ros2cli/node/strategy.py#L25

Hangs within this method. Issue: #ros2/ros2/issues/1093

can recreate with command: ros2 topic list (hangs with constant increase of memory allocation until manually killed)

and directly recreate with:

/root/wsdev/src/jtbot/src/topicList.py 
lv = ListVerb()
v.main(args=None)

Environment:

ros-foxy-desktop/focal,now 0.9.2-1focal.20210226.004308 amd64 [installed]
Docker ubuntu 20.04 
python3.8/focal-updates,focal-security,now 3.8.5-1~20.04.2 amd64 [installed,automatic]

About this issue

  • Original URL
  • State: open
  • Created 6 years ago
  • Comments: 18 (3 by maintainers)

Most upvoted comments

I’m still having the same issue on my system.

Ubuntu Version 22.04
Linux austin-greisman 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
ros-humble-ros2cli/jammy,now 0.18.4-1jammy.20221207.031440 amd64 [installed,automatic]
ros-humble-ros2controlcli/jammy 2.18.0-1jammy.20221207.043415 amd64

ros-humble-cyclonedds-dbgsym/jammy 0.9.1-1jammy.20221108.154039 amd64
ros-humble-cyclonedds/jammy,now 0.9.1-1jammy.20221108.154039 amd64 [installed,automatic]

It seems the only temporary fix is restarting my system. ros2 daemon stop && ros2 daemon start also hangs…

I first noticed this issue while I was debugging C++ code. It seemed to be causing issues with Cyclone

Thank you for your advice @audrow I’m now using Humble with Ubuntu 22.04 and it’s working fine

I’m using osrf/ros:foxy-desktop as the base image for my docker. The issue is random and I can’t really detect a pattern to it yet. It happens when I run my application and then I want to list topics and nodes. Closing the application doesn’t seem to help. When it happens, only a reboot of the host seems to fix it. Anyway, I will keep trying to get more information on the failure mode.

Had this same issue when trying to run ROS2 Humble through a Ubuntu 22.04 Docker container on an Arch Linux setup. Rerunning/rebuilding the container didn’t fix the issue for me either, but the solution that worked for me was to run the command ros2 topic list or ros2 node list with the --no-daemon flag.

Haven’t yet tested with any other ROS distributions, but this solution should work there too.

Hi,

Same issue here. The only solution I found so far is to reboot.

I have the same issues, indeed using Cyclone too.

Yeah. All I can say is that it is not very repeatable but it happens about once or twice a day for me in repeated use. Will keep trying to gather more information. If there is something you want me to look at when this happens, let me know.