Closed chenheamazon closed 2 years ago
Assigning to @SeanCurtis-TRI for initial disposition.
I suspect that this got resolved with #13676.
You should see the benefit in the next release (or in master). Based on what the issue says, you should be able to reduce the number of collision geometries to around 100 (to limit the number of contacts to <= 128) and be ok. Once you have access to master (or the next release), you won't have to live with that artificial constraint.
FYI #13676 is available as of v0.20.0 (and v0.21.0, etc.) tags.
I'm surprised; I went looking in the release notes and didn't see it. But I hadn't actually dug in the commit history to confirm it was included.
Oops...because it's here.
@chenheamazon Did you ever have the chance to confirm that the problem has gone away?
Closing because there's been no action for 1.5 years.
This is on commit 79200833ded29b88f01a28b74afacdd9d0323e87 from June 1, 2020
When I try to run the simple_gripper built in example, and change the number of collision geometry in the example https://github.com/RobotLocomotion/drake/blob/master/examples/simple_gripper/simple_gripper.cc#L67 (this line here) from 8 to 300, it causes a segfault. We have a similar use case where too many registered collision geometry causes a segfault and we suspect that this is the same issue.