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 with continuous collision checking if collision object is BVHModel #10

Open
clemense opened this issue Nov 29, 2018 · 3 comments

Comments

@clemense
Copy link

clemense commented Nov 29, 2018

As the title says it: I get a segmentation fault if I try to do a continuous collision check with a collision object that is created with a fcl.BVHModel. Is this expected behavior?

The bug can be reproduced by replacing cyl with mesh in line 111 of example.py:

dist = fcl.continuousCollide(fcl.CollisionObject(box, fcl.Transform()),
                             fcl.Transform(np.array([5.0, 0.0, 0.0])),
                             fcl.CollisionObject(mesh, fcl.Transform(np.array([5.0,0.0,0.0]))),
                             fcl.Transform(np.array([0.0, 0.0, 0.0])), 
                             req, res)
@mmatl
Copy link
Collaborator

mmatl commented Nov 29, 2018

This is not expected behavior. I'll try to replicate and fix when I have time in the next few days.

@clemense
Copy link
Author

Is there any news on this? Is it hard to replicate?

@clemense
Copy link
Author

clemense commented Jan 24, 2019

There's a small mistake in the example.py when constructing the fcl.BVHModel. The arguments of mesh.beginModel are swapped. Still, it doesn't make a difference in this particular case.
Just to make sure I'm not trying to hunt something nonexistent; can anybody reproduce this bug?
@mmatl

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

2 participants