ros2 / ros2/rclcpp

Publisher cleanup via service call results in deadlock on Jazzy

Open
#2,763 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

more-information-needed
Dominant language
C++
Stars
805
Forks
564
Avg merge
1d 17h
Merged PRs (30d)
27

Description

Relevant issue here:
https://github.com/luxonis/depthai-ros/issues/657
Short description:
When using a service for resetting the driver's state (mostly cleaning up classes that have publishers inside them), the driver has a high chance to hang without response in rclcpp::Executor::wait_for_work (rcl_wait/rmw_wait). This was thought to be fixed by assigning Reentrant CB groups to services that correspond that call this cleanup, but it seems that it didn't help in the end.
The issue has been observed on both Cyclone and FastDDS RMW.
Humble and Noetic versions of the driver don't experience this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Jazzy-only hang described at rclcpp::Executor::wait_for_work, including the rcl_wait/rmw_wait path, and compare behavior with Humble and Noetic. Investigate whether Reentrant callback groups affect cleanup services, using both Cyclone and FastDDS; done means the service returns reliably without the executor deadlocking.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.