Search Issue Tracker

Fixed

Fixed in 6000.3.0b6, 6000.4.0a3

Votes

0

Found in

6000.3.0b4

6000.4.0a1

Issue ID

UUM-121092

Regression

No

Crash on PhysicsComposer2D::IsValid when calling PhysicsComposer.isValid in a class destructor after the object has been destroyed

-

This comes from the following discussion: https://discussions.unity.com/t/lowlevelphysics2d-chaingeometry-more-properties-methods-expected/1688135/11

How to reproduce:
1. Open the attached “IN-119159.zip” project
2. Open the “SampleScene”
3. Enter Play Mode
4. Exit Play Mode
5. Observe the crash

Reproducible in: 6000.3.0a5, 6000.3.0b4, 6000.4.0a1
Could not test with: 2023.1.0a1, 6000.3.0a4, 6000.0.59f1, 6000.2.7f1 (PhysicsComposer does not exist)

Note: If the crash does not reproduce, uncomment the [ExecuteAlways] attribute in the Test1 class and try again

First few lines of stacktrace:
0x00007FF9423CCE8E (Unity) PhysicsComposer2D::IsValid 0x00007FF94249721D (Unity) PhysicsComposerScripting2D_CUSTOM_Composer_IsValid
0x000001AB4CB5C6F2 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.LowLevelPhysics2D.PhysicsComposerScripting2D:Composer_IsValid_Injected (UnityEngine.LowLevelPhysics2D.PhysicsComposer&)
0x000001AB4CB5C593 (Mono JIT Code) UnityEngine.LowLevelPhysics2D.PhysicsComposerScripting2D:Composer_IsValid (UnityEngine.LowLevelPhysics2D.PhysicsComposer)
0x000001AB4CB5C483 (Mono JIT Code) UnityEngine.LowLevelPhysics2D.PhysicsComposer:get_isValid ()
Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues