Search Issue Tracker

Active

Under Consideration for 6000.5.X

Votes

0

Found in

6000.0.66f1

6000.3.6f1

6000.4.0b6

6000.5.0a5

Issue ID

UUM-133588

Regression

No

Crash on MeshRenderer::DispatchUpdate when disabling the second Mesh Renderer on a GameObject

Mesh

-

Steps to reproduce:
1. Open the “user’s attached project”
2. Open the “Assets/Resources/LevelElements/Transitions/t_ministry_street.prefab” Prefab through the Project window
3. Select the ''Box2309” GameObject through the Hierarchy
4. Note that there are two “Mesh Renderer” Components attached to the GameObject
4. Disable the second “Mesh Renderer” Component

Reproducible with versions: 2023.1.0a26, 6000.0.66f1, 6000.3.6f1, 6000.4.0b6, 6000.5.0a5

Reproducible on: macOS 15.7.2 (M1 Max), Windows 11
Not reproducible on: no other environment tested

Notes:
- Disabling the first “Mesh Renderer” does not cause the crash
- Deleting the second “Mesh Renderer” does not cause the crash

First few lines of StackTrace:
#0 0x000001052dfed0 in MeshRenderer::DispatchUpdate(MeshBoundsJobData, TransformChange const, unsigned int)
#1 0x000001051d5a24 in RendererUpdateManager::UpdateSingleRenderer(Renderer&, RendererScene&)
#2 0x0000010525860c in Renderer::GetWorldAABB(AABB&)
#3 0x000001051ed8b8 in RendererScripting::GetClosestReflectionProbes(Renderer, ScriptingObjectPtr)
#4 0x00000104bd2a00 in Renderer_CUSTOM_GetClosestReflectionProbesInternal(void
, ScriptingBackendNativeObjectPtrOpaque*)

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.