-
Notifications
You must be signed in to change notification settings - Fork 376
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
Crash afer overflowing maxSolverFrictionProgress (PxU16) #326
Comments
Hi @ikkah, thanks for reporting. |
Looks like I can reproduce the crash with this modified version of SnippetContactReportCCD ("checked" build config, MSVC). It's a slightly ridiculous setup with a million triangle meshes, but not that different from the actual use-case I have, to be honest.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Library and Version
v5.4.2-106.1 (latest available)
Also reproduced with 5.3.1.
Operating System
Windows 10
Steps to Trigger Behavior
Unfortunately I don't have a test case I could share, but the issue occurs in situations where more than 2^16 contacts are generated.
Articulations are not used in the scene.
Expected Behavior
I'd expect PhysX to error or warn without crashing, possibly omitting the contacts over 2^16.
Actual Behavior
There is an overflow of maxSolverFrictionProgress in recordStaticConstraint() (DyConstraintPartition.cpp).
PhysX eventually crashes with the following call stack:
I couldn't quite figure out the connection between the overflow and the subsequent crash, but the crash seems to happen every time after the overflow.
Please let me know if you need more information.
The text was updated successfully, but these errors were encountered: