-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
epa3.rs panic in closest_points
#253
Comments
I ran into this issue today. I don't use any sort of rigid bodies or parent-child relationships. I simply add my static model, call step and boom. I've encountered this in both Parry 0.17 and 0.14. I'm now wondering how to reproduce it myself |
Here's a repro with just two triangles. I simplified it as much as I could, even removing digits after decimal points.
|
I further simplified the repro to just the following code: let mesh1 = Triangle::new(
Point3::new(-13.174434, 1.0, 8.736801),
Point3::new(3.5251038, 1.0, 12.1),
Point3::new(3.2048466, 1.0, 12.218325),
);
let mesh2 = Triangle::new(
Point3::new(-1.63, 0.0, 11.19),
Point3::new(-2.349647, 0.0, 11.037681),
Point3::new(-2.349647, 1.0, 11.037681),
);
query::details::contact_support_map_support_map_with_params(
&Isometry3::identity(),
&mesh1,
&mesh2,
0.00999999977,
&mut VoronoiSimplex::new(),
None,
); |
Didn't want to hijack #246 since my conditions are different, but I am running into my own crash for the epa3.rs
*self.heap.peek()
statement. I can reliably encounter it in the wild, but despite my best efforts to reproduce it outside of that environment I've been unable to.I've modified the affected statement (and added some
Debug
annotations where appropriate) to be able to capture the state of the process at the time of failure:...which results in the following output:
Despite it not actually panicking, I'm also pasting my attempt to reproduce my problems:
The text was updated successfully, but these errors were encountered: