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
After the program has exited, launch the rosnode list command and you will see that the node opened by the example program is still registered:
user@iiticubws003:~/yarp_rosnode_test/build$ rosnode list
/nodeThatWillNotBeUnregisteredFromRosMaster
/rosout
The text was updated successfully, but these errors were encountered:
traversaro
changed the title
ROS Nodes registered in ROS Master using the yarp::os::Node are not unregisterd on exit
ROS Nodes registered in ROS Master using the yarp::os::Node are not unregisterd on process exit
Sep 26, 2017
traversaro
changed the title
ROS Nodes registered in ROS Master using the yarp::os::Node are not unregisterd on process exit
ROS Nodes registered in ROS Master using the yarp::os::Node are not unregistered when the object is deleted/on process exit
Sep 26, 2017
If you create a ROS Nodes using YARP, it will not be properly unregistered from the ROS Master once the process is closed.
How to reproduce
Compile and run the example in https://gist.github.com/traversaro/e34c849fff2dd481625ae7a40edb173c#file-main-cpp-L15 , on a computer in which ROS is correctly configured and roscore is running.
After the program has exited, launch the
rosnode list
command and you will see that the node opened by the example program is still registered:The text was updated successfully, but these errors were encountered: