Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X
Votes
0
Found in
2021.2
2021.2.11f1
2022.1
2022.2
Issue ID
1404273
Regression
No
Crash when calling Graphics.RenderMesh for a Mesh that was destroyed
Reproduction steps:
1. Open the attached project "Test_script"
2. Open "Assets/Scene/Sample Scene" scene
3. Disable "GameObject" from the Hierarchy
Expected result: Error is thrown that Mesh can't be found
Actual result: Editor crashes
Reproducible with: 2021.2.11f1, 2022.1.0b7, 2022.2.0a5
Could not test with: 2019.4.36f1, 2020.3.28f1 (Graphics.RenderMesh not found)
First lines of stacktrace:
0x00007ff6316fd598 (Unity) delete_object_internal_step1
0x00007ff6316f9d10 (Unity) DestroySingleObject
0x00007ff631a16fcd (Unity) DestroyObjectHighLevel_Internal
0x00007ff631a16b64 (Unity) DestroyObjectHighLevel
0x00007ff631d61ccf (Unity) Scripting::DestroyObjectFromScriptingImmediate
0x00007ff630f78803 (Unity) Object_CUSTOM_DestroyImmediate
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][iOS] The keyboard closes and re-opens when consecutive input fields are selected
- Complex Sub Graph connected to a Voronoi node is ignored when the shader gets applied as a Material
- Compute Shader property not set error when entering play mode with path tracing and PBR sky
- "WebGL Publish" detects WebGL module and allows building when it is installed without restarting the project
- Editor is non-responsive and flickers when multiple Water System instances are enabled
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a12
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.4f1