Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
5
Found in
2019.1.0b6
2019.1.7f1
2019.2.0a7
2019.3.0a1
Issue ID
1169786
Regression
No
The unused shaders are still being tracked when Asynchronous Shader compilation is enabled
How to reproduce:
1. Open the "SampleScene" in the attached project "case_1169786"
2. Go to Edit -> Project Settings -> Graphics
3. Click on the "Clear" button at the bottom of the window
4. Disable the "Cube" GameObject
5. Repeat steps 2 and 3 one more time
Expected results: Tracked Shader quantity is lower when "Cube" is disabled
Actual results: Tracked Shader quantity is the same in both cases
Reproducible with: 2019.1.11f1, 2019.2.0b10, 2019.3.0a10
Not reproducible with: 2017.4.30f1, 2018.4.4f1, 2019.1.0b5, 2019.2.0a6
Additional notes:
1. The first affected versions of each stream are the ones where Async Shader compilation was introduced. Disabling Async Shader compilation will solve this issue.
2. The reason why there are more tracked shaders when Async Shader compilation is on is that Cube GameObject shaders remain tracked even though this GameObject is disabled.
-
stevensrmiller
Jul 17, 2019 13:19
Don't just disable the Cube. Delete it. This reduces the tracked count when it is cleared in other versions.
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b9