Search Issue Tracker
Fixed in 2022.2.X
Crash on delete_object_internal_step1 when using Graphics.RenderMesh to render a lot of Sprites to screen
How to reproduce:
1. Open the attached project from "crashSprite.zip"
2. Open Scene "Main"
3. Enter and Exit Play Mode (do this couple of times if it doesn't crash after the first)
Reproducible with: 2021.2.13f1, 2022.1.0b9, 2022.2.0a5
Couldn't test with: 2019.4.36f1, 2020.3.30f1 (nvidia module missing?)
First lines of the stack trace:
0x00007ff79917d758 (Unity) delete_object_internal_step1
0x00007ff799179ed0 (Unity) DestroySingleObject
0x00007ff7994975bd (Unity) DestroyObjectHighLevel_Internal
0x00007ff799497154 (Unity) DestroyObjectHighLevel
0x00007ff7994a1be7 (Unity) DestroyWorldObjects
0x00007ff79a6c5cc1 (Unity) EditorSceneManager::RestoreSceneBackups
Feb 23, 2022 21:38
I've been having the same issue, and I realized that It doesn't happen if I assign a camera to the RenderParams object. When the camera is set to null and exiting play mode, it crashes every time.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Depth is not rendered in a depth-only camera which is set up by a custom script
- The Scene\Game view is grey when two "Universal Additional Camera Data" scripts are attached to the camera
- NullReferenceException error thrown when changing Scenes in Play Mode
- Crash on "'anonymous namespace'::ConvertFBXShapes" when importing an FBX file
- Crash on Transform::RemoveFromParent when Object.DestroyImmediate() is called on Transform
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a9