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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment