Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.1.2f1
2019.2.0a1
2019.3.0a1
Issue ID
1156199
Regression
Yes
InvalidOperationException thrown and performance drop when selecting a Mesh inside Scene View with more than 63 submeshes
Reproduction steps:
1. Open the attached Project from "New Unity Project.zip"
2. Open the "Main" Scene
3. Select the "MeshRenderer" GameObject
Expected result: No exceptions are logged inside the Console window
Actual result: Exceptions are logged inside the Console window and performance drops
Reproduces on: 2018.3.0a1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
Does not reproduce on: 2017.4.26f1
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
When we are rendering material previews it's possible to exceed the limit of 63 that exists due to preview scene limitations. We need to be more careful about returning preview scenes after each render so they can be shared.