iOS crash visualiseConstraint

We have access to the bugly SDK. Crash report is below

SIGBUS
BUS_ADRALN

physx::PxVehicleConstraintShader::visualiseConstraint(physx::PxConstraintVisualizer&, void const*, physx::PxTransform const&, physx::PxTransform const&, unsigned int) + 16337976
physx::PxVehicleConstraintShader::visualiseConstraint(physx::PxConstraintVisualizer&, void const*, physx::PxTransform const&, physx::PxTransform const&, unsigned int) + 14215868
physx::PxVehicleConstraintShader::visualiseConstraint(physx::PxConstraintVisualizer&, void const*, physx::PxTransform const&, physx::PxTransform const&, unsigned int) + 14216032

The stack info is repeat many times. It looks like recursive call ‘visualiseConstraint(…)’, but I can’t find any useful imfomation about this function

I encountered this crash as well. Have you fixed it?

I encountered this crash as well. Have you fixed it?

encountered this crash + 1,Is anyone solve it?

encountered this crash too

Does anyone have any updates on this?

The error you provided indicates a SIGBUS signal with a BUS_ADRALN code, which indicates that the program attempted to access a memory address that is not properly aligned.

The stack trace suggests that the issue is related to the visualiseConstraint() function of the PhysX vehicle constraint shader. It seems that this function is being called recursively, which could be causing the memory alignment issue.

Without more context or information about your code, it’s difficult to provide a specific solution. However, you could try the following steps to further diagnose and potentially resolve the issue:

  1. Check your code for any infinite loops or recursive function calls that could be causing the visualiseConstraint() function to be called repeatedly.
  2. Verify that you are passing valid arguments to the visualiseConstraint() function. Ensure that the memory addresses being passed to the function are properly aligned and that the function is being called with the expected parameters.
  3. Check the memory allocation and deallocation in your code to ensure that it is being done correctly. Memory mismanagement could cause memory alignment issues, which could result in a SIGBUS signal with a BUS_ADRALN code.
  4. Consider upgrading to a newer version of the PhysX SDK or checking for any known issues related to this function in the current version you are using.
  5. Analyze the crash dump and stack trace using a debugger or profiling tool to gain more insights into the cause of the issue.

If you’re still having trouble after trying these steps, you could also consider reaching out to the support team for the bugly SDK, as they may have more experience with this specific issue and be able to provide additional guidance.