global_planner crashes when orientation mode is any of interpolation types? [closed]
Hi,
I am using ROS Kinetic on Ubuntu 16.04, and am not sure if I have wrongly configured any of the files, or whether this occurs regardless of the configuration?. Any thoughts/experiences in this regard would be helpful.
I have repeatedly observed the following for the global_planner planning in the navigation stack for both, move_base and move_base_flex:
When an invalid (in my case, inaccessible) goal was given to the planner with the orientation mode set to either None or Forward, the planner simply reports an error "Failed to get a plan." and continues its retries/resets, however configured.
However, with all the remaining configuration set same, but the orientation mode switched to either Interpolate or Forward then Interpolate, the planner reports the "Failed to get a plan." error once and then crashes the move_base/move_base_flex node.
I feel this is more a topic for an issue to report a crash on the
navigationrepository than a post on ROS Answers.Thought so, but just wanted to be a little more certain about it, before reporting there, in case somebody could elaborate upon it..
If you can repeatedly crash a component by just varying its input, I would say that is never acceptable or explainable behaviour and should be fixed.
That makes sense, thanks for the patience! Will close this and report the issue.
If you do post an issue, please keep things connected and comment here with a link to your issue.
posted issue here: https://github.com/ros-planning/navig...