Search Issue Tracker
Fixed in 5.6.0f3
Fixed in 5.4.X, 5.5.X, 5.6.X, 2017.1.X
Votes
2
Found in
5.5.1p4
Issue ID
885275
Regression
Yes
Crash in GetBuildUsageTagFromAssets when the project has ShaderVariants
To reproduce:
1. Open attached project;
2. Open "test" scene;
3. Go to Graphics Settings (Edit > Project Settings > Graphics) and set the Size of Preloaded Shaders to 0;
4. Build the project;
5. Go to Graphics Settings and set the Size of Preloaded Shaders to 1;
6. Repeat step 4.
Expected result: no crash when the Project includes ShaderVariants.
Actual result: Editor crashes.
Reproducible on versions: 5.5.1p4, 5.6.0b10, 2017.1.0a1.
Not reproducible on versions: 5.5.1p3.
Regression found on version: 5.5.1p4.
Note: on version 5.4.4p4 Editor crashes with a different Stack Trace.
Comments (1)
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 PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
einWikinger
Apr 21, 2017 14:28
Had this today, too, after adding the new post processing effects to our project. I removed the old, standard-assets based post effects from the project and our old shader variant collection may have still referenced shaders that I deleted.
I then removed the variant collection from the graphics settings, and it built again. As a next step, I re-saved a new variant collection after playing through the game and configuring it as the preload collection, and that worked again.
So maybe it has also something to do with stale shader references in the variant collection.
Reproduced on 5.5.2p3