-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] node deadlocks and roudi segfaults in ros galactic. #1445
Comments
robotechvision
pushed a commit
to robotechvision/cyclonedds
that referenced
this issue
Oct 28, 2022
eboasson
pushed a commit
that referenced
this issue
Jan 19, 2023
eboasson
pushed a commit
to eboasson/cyclonedds
that referenced
this issue
Mar 14, 2023
eboasson
pushed a commit
that referenced
this issue
Mar 14, 2023
I believe this issue might have been resolved here eclipse-iceoryx/iceoryx#1740 after #1463. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In iceoryx the following bug was reported: eclipse-iceoryx/iceoryx#1740
In short we have a high frequency ROS publisher which sends data and a listener application which receives the first couple of thousand samples and then seems to end up in a dead lock.
This deadlock seems to cause also a seg-fault in roudi when the listener is terminated with a kill signal.
Furthermore, when the listener is in this deadlock roudi cannot be terminated any longer.
This repository provides examplary code and instructions on how to produce the issue: https://github.com/ceccocats/iceoryx_bug
I suspect that we have here a couple of issues. A deadlock in the listener should never cause roudi to be no longer able to terminate, this we have to investigate further on iceoryx side. Also the segfault which is caused when the deadlocked listener is killed.
But I think that the problem maybe originates somewhere in dds therefore I created the ticket.
The text was updated successfully, but these errors were encountered: