-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
MPPI path_follow_critic crash #3456
Comments
I can say that I haven't seen this before and hasn't been reported during our extensive beta testing either. Interesting, very interesting I suspect its perhaps the But then the question comes by does this only happen sometimes since we set a The other possible situation is that your path is empty or only 1 point long so the length of |
I've seen it 4-5 times so far and only with LETHAL_OBSTACLE
I did not check yet, will do tomorroe
Will also check that
It did not seem to happen at a particular distinguishible moment but I could be wrong. I'm pretty sure it happens when we are still far from the goal. |
OK. I didn't really think that was the case anyway but was worth just outlining anything I could see as a potential cause. There are protections and exceptions that should be thrown for trivial paths anyway long before that point (but I wasn't 100% sure there wasn't a hole - but if you didn't see it on approach to goal only, we can discard that).
Thanks 👍 I highly suspect that's it. |
I see this log before the crash, seems related |
I think you were right here. The crash happens when path_segments_count is 1 because the vector
I guess this is the reason https://stackoverflow.com/questions/16620222/vector-going-out-of-bounds-without-giving-error. Replacing [] with at() does indeed yield an error every time |
Awesome, thanks for the report! There’s always 4 bugs no matter how much testing I do… |
Thanks for fixing this ! |
No problem! I did see another crash after this fix, if I remember correctly somewhere in the same critic, but didn't give it much attention as I thought it would reproduce but it hasn't yet. So you might find more, I'll keep an eye open as well |
Bug report
Required Info:
Steps to reproduce issue
I still can't tell what are the preconditions leading to this crash but I get it frequently (I'll add more info as I discover them)
Additional information
The text was updated successfully, but these errors were encountered: