Rigid Body Animation segmentation fault after canceled move of passive rigid body #104007

New Issue

System Information
Operating system:
"Ubuntu 20.04.5 LTS" XFCE window manager
32 GB RAM

Graphics card:
NVidia GTX1080 (Zotac Mini) -- Driver Version: 390.157

Blender Version
Broken: 3.4.1
Worked: 3.5

Short description of error
Forcing change to rigid body physics simulation by grabbing passive rigid body object (conveyor belt ) and then canceling results in segmentation fault on play of animation.

Exact steps for others to reproduce the error

Open attached Blend file
In 3D viewport, select belt mesh
NEW MISSED STEP Play Animation without touching anything (note crazy physics)
g, drag, escape the "Belt" object to force physics cache to update.

Play animation. Segmentation fault should occur.

convetor.belt09.blend

**System Information** Operating system: "Ubuntu 20.04.5 LTS" XFCE window manager 32 GB RAM Graphics card: NVidia GTX1080 (Zotac Mini) -- Driver Version: 390.157 **Blender Version** Broken: 3.4.1 Worked: 3.5 **Short description of error** Forcing change to rigid body physics simulation by grabbing passive rigid body object (conveyor belt ) and then canceling results in segmentation fault on play of animation. **Exact steps for others to reproduce the error** - Open attached Blend file - In 3D viewport, select belt mesh - **NEW MISSED STEP** Play Animation without touching anything (note crazy physics) - g, drag, escape the "Belt" object to force physics cache to update. # Play animation. Segmentation fault should occur. [convetor.belt09.blend](https://archive.blender.org/developer/F14176451/convetor.belt09.blend)

Added subscriber: @loopdloop

Added subscriber: @iss

Can't reproduce crash here. Please upload file /tmp/convetor.belt09.crash.txt after crash

Changed status from 'Needs Triage' to: 'Needs User Info'

In #104007#1476906, @iss wrote:
Can't reproduce crash here. Please upload file /tmp/convetor.belt09.crash.txt after crash

Hi Richard, Thanks for taking a look at this. Please note the edit to the reproduce steps.

Also, I'm new to debugging Blender. The crash file was basically empty convetor.belt09.crash.txt

so I tried with
blender -d
But, same result. I see a whole slew of debug options. Can you suggest some?

If not, no worries, I'll do some more reading.

> In #104007#1476906, @iss wrote: > Can't reproduce crash here. Please upload file /tmp/convetor.belt09.crash.txt after crash Hi Richard, Thanks for taking a look at this. Please note the edit to the reproduce steps. Also, I'm new to debugging Blender. The crash file was basically empty [convetor.belt09.crash.txt](https://archive.blender.org/developer/F14177253/convetor.belt09.crash.txt) so I tried with blender -d But, same result. I see a whole slew of debug options. Can you suggest some? If not, no worries, I'll do some more reading.

Starting Blender with:

blender --debug-all --debug-value 99 --debug-python

and reproducing the crash. File now contains convetor.belt09.crash.txt

Also note earlier edit where I could not duplicate in 3.5.0 alpha.

Can duplicate pretty consistently in 3.4.1

This may be more useful. Command line capture to file:

blender --debug-all --debug-value 99 --debug-python > blender_stderr_stdout.txt 2>&1
blender_stderr_stdout.txt

Starting Blender with: blender --debug-all --debug-value 99 --debug-python and reproducing the crash. File now contains [convetor.belt09.crash.txt](https://archive.blender.org/developer/F14177297/convetor.belt09.crash.txt) Also note earlier edit where I could not duplicate in 3.5.0 alpha. Can duplicate pretty consistently in 3.4.1 This may be more useful. Command line capture to file: blender --debug-all --debug-value 99 --debug-python > blender_stderr_stdout.txt 2>&1 [blender_stderr_stdout.txt](https://archive.blender.org/developer/F14177313/blender_stderr_stdout.txt)

Changed status from 'Needs User Info' to: 'Needs Triage'

Added subscriber: @lichtwerk

Thanks for updating steps, unfortunately I am still not able to reproduce the issue. Could be linux related though. @lichtwerk, can you check?

Just to rule out the video card/drivers I tested on an older Linux PC using two versions of Blender.

Results:

$ lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770]

$ grep PRETTY /etc/os-release 
PRETTY_NAME="Ubuntu 18.04.6 LTS"

$ ls /data/bin/blender-3.* -d
/data/bin/blender-3.1.0-linux-x64        # Cannot duplicate
/data/bin/blender-3.4.1-linux-x64        # Can duplicate -- same version as initially reported

Just to rule out the video card/drivers I tested on an older Linux PC using two versions of Blender. Results: ``` $ lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] $ grep PRETTY /etc/os-release PRETTY_NAME="Ubuntu 18.04.6 LTS" $ ls /data/bin/blender-3.* -d /data/bin/blender-3.1.0-linux-x64 # Cannot duplicate /data/bin/blender-3.4.1-linux-x64 # Can duplicate -- same version as initially reported ```

Added subscriber: @PratikPB2123

Changed status from 'Needs Triage' to: 'Confirmed'

Hi, I can confirm on Windows. Crash seems to be fixed after 3.4 release. I'll find the exact commit shortly.

Stack trace:
blender.exe         :0x00007FF7E83B1D40  btConvexShape::localGetSupportVertexWithoutMarginNonVirtual
blender.exe         :0x00007FF7E8417120  btComputeSupport
blender.exe         :0x00007FF7E8418A40  btGjkPairDetector::getClosestPointsNonVirtual
blender.exe         :0x00007FF7E8400490  btConvexConvexAlgorithm::processCollision
blender.exe         :0x00007FF7E83A9460  btCollisionDispatcher::defaultNearCallback
blender.exe         :0x00007FF7E83A9A20  btCollisionPairCallback::processOverlap
blender.exe         :0x00007FF7E840DD30  btHashedOverlappingPairCache::processAllOverlappingPairs
blender.exe         :0x00007FF7E840DDD0  btHashedOverlappingPairCache::processAllOverlappingPairs
blender.exe         :0x00007FF7E83A95C0  btCollisionDispatcher::dispatchAllCollisionPairs
blender.exe         :0x00007FF7E83AEC00  btCollisionWorld::performDiscreteCollisionDetection
blender.exe         :0x00007FF7E83C1A80  btDiscreteDynamicsWorld::internalSingleStepSimulation
blender.exe         :0x00007FF7E83C2E10  btDiscreteDynamicsWorld::stepSimulation
blender.exe         :0x00007FF7E30C6340  BKE_rigidbody_do_simulation
blender.exe         :0x00007FF7E30C69B0  BKE_rigidbody_eval_simulation
blender.exe         :0x00007FF7E339A920  blender::deg::`anonymous namespace'::evaluate_node
blender.exe         :0x00007FF7E339A6C0  blender::deg::`anonymous namespace'::deg_task_run_func
blender.exe         :0x00007FF7E8C92780  tbb::internal::function_task<Task>::execute
tbb.dll             :0x00007FFC2F1FF220  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFC2F1FF220  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFC2F1F4FD0  tbb::interface7::internal::isolate_within_arena
tbb.dll             :0x00007FFC2F1FA120  tbb::task_scheduler_init::terminate
tbb.dll             :0x00007FFC2F1FD800  tbb::thread_bound_filter::try_process_item
tbb.dll             :0x00007FFC2F1FD800  tbb::thread_bound_filter::try_process_item
ucrtbase.dll        :0x00007FFC5B7B6BB0  recalloc
KERNEL32.DLL        :0x00007FFC5DE85590  BaseThreadInitThunk
ntdll.dll           :0x00007FFC5E104830  RtlUserThreadStart```

Hi, I can confirm on Windows. Crash seems to be fixed after 3.4 release. I'll find the exact commit shortly. ```lines=10 Stack trace: blender.exe :0x00007FF7E83B1D40 btConvexShape::localGetSupportVertexWithoutMarginNonVirtual blender.exe :0x00007FF7E8417120 btComputeSupport blender.exe :0x00007FF7E8418A40 btGjkPairDetector::getClosestPointsNonVirtual blender.exe :0x00007FF7E8400490 btConvexConvexAlgorithm::processCollision blender.exe :0x00007FF7E83A9460 btCollisionDispatcher::defaultNearCallback blender.exe :0x00007FF7E83A9A20 btCollisionPairCallback::processOverlap blender.exe :0x00007FF7E840DD30 btHashedOverlappingPairCache::processAllOverlappingPairs blender.exe :0x00007FF7E840DDD0 btHashedOverlappingPairCache::processAllOverlappingPairs blender.exe :0x00007FF7E83A95C0 btCollisionDispatcher::dispatchAllCollisionPairs blender.exe :0x00007FF7E83AEC00 btCollisionWorld::performDiscreteCollisionDetection blender.exe :0x00007FF7E83C1A80 btDiscreteDynamicsWorld::internalSingleStepSimulation blender.exe :0x00007FF7E83C2E10 btDiscreteDynamicsWorld::stepSimulation blender.exe :0x00007FF7E30C6340 BKE_rigidbody_do_simulation blender.exe :0x00007FF7E30C69B0 BKE_rigidbody_eval_simulation blender.exe :0x00007FF7E339A920 blender::deg::`anonymous namespace'::evaluate_node blender.exe :0x00007FF7E339A6C0 blender::deg::`anonymous namespace'::deg_task_run_func blender.exe :0x00007FF7E8C92780 tbb::internal::function_task<Task>::execute tbb.dll :0x00007FFC2F1FF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFC2F1FF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFC2F1F4FD0 tbb::interface7::internal::isolate_within_arena tbb.dll :0x00007FFC2F1FA120 tbb::task_scheduler_init::terminate tbb.dll :0x00007FFC2F1FD800 tbb::thread_bound_filter::try_process_item tbb.dll :0x00007FFC2F1FD800 tbb::thread_bound_filter::try_process_item ucrtbase.dll :0x00007FFC5B7B6BB0 recalloc KERNEL32.DLL :0x00007FFC5DE85590 BaseThreadInitThunk ntdll.dll :0x00007FFC5E104830 RtlUserThreadStart```

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Rigid Body Animation segmentation fault after canceled move of passive rigid body #104007

Play animation. Segmentation fault should occur.