Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.2.X
Votes
1
Found in
2018.4
2019.2.0f1
2021.1
Issue ID
1188507
Regression
No
Editor crashes on BaseRenderer::FlattenCustomProps when adding materials in the Mesh Renderer after SetPropertyBlock was called
To reproduce:
1. Open the user's attached "PropertyBlockMeshRendTest.zip" project
2. Load the "test" scene
3. Select the "Sphere" GameObject in the Hierarchy window
4. Click on the "Set Color Now" checkbox in the Inspector window
5. Change the size of Materials in the Mesh Renderer component
--Observe the crash
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.10f1, 2020.2.0b8, 2021.1.0a2
Could not test with 2017.4.32f1 because there is no SetPropertyBlock(MaterialPropertyBlock properties, int materialIndex) method
Note: calling SetPropertyBlock(MaterialPropertyBlock properties) instead of SetPropertyBlock(MaterialPropertyBlock properties, int materialIndex) does not crash the Editor when changing Materials count in the Mesh Renderer
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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a4
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b12
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.15f1
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.31f1