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
I've searched other issues and no duplicate issues were found.
I'm convinced that this is not my fault but a bug.
Description
When shutting down Autoware that utilizes ROS2, there is an observed issue where not all ROS2-related resources are fully released. This incomplete release of resources causes problems during subsequent attempts to launch Autoware, preventing normal initialization. Shutting down using Ctrl+C does not seem to effectively manage the cleanup of all active resources.
Expected behavior
Upon shutting down Autoware, all resources, especially those tied to ROS2, should be fully released, ensuring that the system is clean and ready for a new startup without any issues.
Actual behavior
Resources remain engaged or partially active after Autoware is shut down using Ctrl+C. This leads to difficulties when attempting to restart Autoware. The only workaround is either system reboot or forceful termination of all ROS-related processes using commands like pkill -f 'ros'.
Steps to reproduce
Start Autoware with ROS2 integration.
After running some processes, attempt to shut down the system using Ctrl+C.
Hello @sgNicola . Thanks for your sharing. Here I understand that the resources connected to ROS2 remain open after Autoware is closed. Could you explain this a little bit? When you run the ros2 node list command, did you see that there were active nodes? Or do you think TFs are still active?
Checklist
Description
When shutting down Autoware that utilizes ROS2, there is an observed issue where not all ROS2-related resources are fully released. This incomplete release of resources causes problems during subsequent attempts to launch Autoware, preventing normal initialization. Shutting down using Ctrl+C does not seem to effectively manage the cleanup of all active resources.
Expected behavior
Upon shutting down Autoware, all resources, especially those tied to ROS2, should be fully released, ensuring that the system is clean and ready for a new startup without any issues.
Actual behavior
Resources remain engaged or partially active after Autoware is shut down using Ctrl+C. This leads to difficulties when attempting to restart Autoware. The only workaround is either system reboot or forceful termination of all ROS-related processes using commands like pkill -f 'ros'.
Steps to reproduce
Versions
-OS:Ubuntu 20.04
-ROS2: ROS2 galactic
-Autoware: Autoware.universe galactic
Possible causes
Resource Management
Additional context
No response
The text was updated successfully, but these errors were encountered: