Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.8f1
Issue ID
1084309
Regression
No
ApplyShaderState crash when scene loaded additively
Steps to reproduce:
1) Open the attached project.
2) Build and run (Windows, macOS, iOS).
3) Once the scene loads, press the button on the screen.
A crash occurs while loading custom LWRP shaders upon switching the scene.
If the scene containing the shaders is loaded on startup, the crash does not occur.
Reproduces with OpenGL, Metal and DirectX 11.0.
Reproduced on:
2018.2.10f1, 2018.2.8f1
Did not reproduce:
2019.1.0a2
On 2018.3, the scene does not start loading upon pressing the button, but errors are spammed to console on each frame (Xcode):
blueshadercrashdebug[21592:1803773] Execution of the command buffer was aborted due to an error during execution. Ignored (for causing prior/excessive GPU errors) (IOAF code 4)
Tested on:
MacBook Pro (Retina, 15-inch, Mid 2015) macOS 10.13.6
iPhone 8 Plus iOS 12.0
Windows 10
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