Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
0
Found in
2019.2.0b7
2019.2.2f1
Issue ID
1184997
Regression
Yes
Project crashes on opening in ShaderLab::IntShader::PostLoad(Shader*)
How to reproduce:
1. Open the attached Probuilder2.2.zip project
===Crash occurs===
Reproducible wtih: 2019.2.7f2
Not reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.2.0a1-2019.2.0b6, 2019.3.0b5, 2020.1.0a7
Notes:
- Deleting Library solves the issue, bus as the project is huge it takes way to long for the user
- User is asking some way to protect the project from crashing
Stack trace:
#0 0x0000010fcfb688 in ShaderLab::IntShader::PostLoad(Shader)
#1 0x00000110f195f3 in Shader::SetGlobalRenderPipeline(core::basic_string<char, core::StringStorageDefault<char> > const&)
#2 0x00000110291b28 in Shader_Set_Custom_PropGlobalRenderPipeline(ScriptingBackendNativeStringPtrOpaque)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment