Fixed bad_alloc in collision_detection::distanceCallback #989
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
v4hn
approved these changes
Aug 20, 2018
There was a problem hiding this comment.
Thank you so much @troizky !
That's quite a bug you found there.
I guess this was painful to debug and I'm ashamed it took us almost a month until the first review...
I approve, please have a look @rhaschke @davetcoleman, we should fix this regression soon.
rhaschke
approved these changes
Aug 20, 2018
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed issue #988
Use method CollisionGeometryData::getID() instead of direct access to object field regardless its type.