Skip to content
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

Segfault calling spawn() from ComputeIK stage in latest ROS 2 version #518

Closed
sea-bass opened this issue Dec 15, 2023 · 5 comments
Closed
Assignees

Comments

@sea-bass
Copy link
Contributor

sea-bass commented Dec 15, 2023

I've just upgraded to the latest version of MoveIt 2 and MTC and running into an issue I could use some help with.

I've partially isolated a new segfault to the ComputeIK stage calling spawn() in this line: https://github.com/ros-planning/moveit_task_constructor/blob/ros2/core/src/stages/compute_ik.cpp#L437 ... which in turn fails in this line: https://github.com/ros-planning/moveit_task_constructor/blob/master/core/src/stage.cpp#L237

The error itself is:

 terminate called after throwing an instance of 'std::out_of_range'
   what():  vector::_M_range_check: __n (which is 12) >= this->size() (which is 12)

Any ideas that could help pinpoint the problem?

@sea-bass
Copy link
Contributor Author

I just saw moveit/moveit2#2615 which may actually point to the root cause, if it's also happening outside MTC?

@sea-bass
Copy link
Contributor Author

Update: I've found that reverting moveit/moveit2#2546 makes this issue go away. Seems to be related to a recent refactor of MoveIt's RobotState type and nothing to do with MTC.

@marioprats marioprats self-assigned this Dec 18, 2023
@marioprats
Copy link
Contributor

This should be (partially) fixed by: #519
The real fix should happen on the MoveIt RobotState side.

@rhaschke
Copy link
Contributor

I don't see how #519 is related to spawn().

@sea-bass
Copy link
Contributor Author

sea-bass commented Dec 18, 2023

Right. It's an underlying MoveIt issue with the RobotState refactor that we ended up finding later. We can close this as it's not related to MTC.

Thank you for looking into this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants