Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
1
Found in
2019.4
2020.1
2020.1.1f1
2020.2
Issue ID
1268659
Regression
No
Crash on PhysicsScene2D::DestroyColliderIgnoreCollisions when loading a scene async
Reproduction steps:
1. Open the project attached by the user
2. Open "scn_gray_1_1" scene and enter Play mode
3. Continue forward to load another scene, then go back to load the previous scene
4. Repeat step 3 until it crashes
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
First lines of the stacktrace:
0x00007FF641138418 (Unity) PhysicsScene2D::DestroyColliderIgnoreCollisions
0x00007FF64111D3E3 (Unity) Collider2D::Deactivate
0x00007FF63FD45148 (Unity) GameObject::ActivateAwakeRecursivelyInternal
0x00007FF63FD44FD5 (Unity) GameObject::ActivateAwakeRecursivelyInternal
0x00007FF63FD44D2F (Unity) GameObject::ActivateAwakeRecursively
Notes:
- Might be related to case 1231211, but that one is already fixed whereas this still reproduces on the newest versions
- I was struggling to test 2019.4.9f1, since the project package integration breaks after downgrading, but it did crash with the same stacktrace when trying to enter Play mode
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when pressing the "Enter" key to select an item in a ListView
- Burst internal compiler errors are thrown when creating a new 2D project
- Tile Paint action disappears from Undo History when Tile Selection tool has been used beforehand
- The pregenerated LightDefinition.cs.hlsl does not match the source LightDefinition.cs when regenerating shader includes
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
Add comment