Search Issue Tracker
Fixed in 2019.3.X
Votes
1
Found in
2019.1.0a10
2019.1.4f1
2019.2.0a1
2019.3.0a1
Issue ID
1158089
Regression
Yes
High CPU and GPU load when a material with certain shaders is displayed in the Inspector
Reproduction steps:
1. Open the attached project named "Case_1158089"
2. Select the "Material_V1" and observe the CPU chart in the Profiler Window
3. Select the "Material_V2" and observe the CPU chart in the Profiler Window again
Expected result: Profiler's readout is the same for both materials
Actual result: Seems like Material_V2 is constantly redrawing the scene which is taxing on both CPU and GPU
Reproducible with: 2019.1.0a10, 2019.1.5f1, 2019.2.0b5, 2019.3.0a5
Not reproducible with: 2017.4.28f1, 2018.4.1f1, 2019.1.0a9
Notes:
Shaders that are affected: Mobile/VertexLit(both versions), Mobile/Unlit, Nature/Terrain/Diffuse
Shaders that are not affected: Standard, Mobile/Bumped Diffuse, Autodesk Interactive
On some versions, the issue stops when a mouse cursor enters the Inspector window(Track_1158089_V2)
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Xarbrough
Jun 19, 2019 19:04
This also affects the builtin Sprites-Default shader.