Search Issue Tracker
Won't Fix
Won't Fix in 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
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting this bug to Unity.
We have identified that the crash occurs when two MeshRenderers exist on the same GameObject, which is not supported by the engine. This configuration cannot be created in current Unity versions and likely originated from a legacy project.
Given the limited impact and severity, we will not be addressing this issue. The solution is to remove one of the MeshRenderers, which will resolve the crash.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting this bug to Unity.
We have identified that the crash occurs when two MeshRenderers exist on the same GameObject, which is not supported by the engine. This configuration cannot be created in current Unity versions and likely originated from a legacy project.
Given the limited impact and severity, we will not be addressing this issue. The solution is to remove one of the MeshRenderers, which will resolve the crash.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.