-
Notifications
You must be signed in to change notification settings - Fork 493
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
move_group segfault when destructing node inside trajectory_execution_manager #1597
Comments
I'm facing another segmentation fault that seems to be only in version
|
@timonegk can you reproduce this error with debug symbols so we can get more detail out of the stack trace to see if it is the same segfault or a different one? If you are using moveit from apt you can install the packages: ros-rolling-rclcpp-dbgsym Then when the segfault happens you should get a stack trace that includes where in the code it is failing. |
I am unfortunately no longer able to reproduce my issue, I'm getting a different error now. I will report back when I know more. |
The issue is back, here is the stack trace:
Looks at least similar to yours, however there is no trajectory_execution_manager. And I think my traceback from october was a different one. This time I reproduced the issue in a clean docker container with the packages
|
isn't this fixed with #2001 |
If I recall correctly #1918 fixed this issue, @samialperen do you mind testing it? |
@JafarAbdi tested #2001 and all good. Thanks. |
This issue still exists for me with version 2.8.0 |
Description
The text was updated successfully, but these errors were encountered: