Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2019.4.18f1
2020.2
2021.1
2021.2
Issue ID
1310201
Regression
No
Shader Compiler crashes when using Interlocked* methods in pixel shader
Reproduction steps:
1. Open the attached "case_1310201.zip" project
2. In the Project window, select Test.shader and compile it
3. Observe the Console window
Expected result: There are no errors
Actual result: Shader compiler errors appear
Reproducible with: 2018.4.32f1, 2019.4.20f1, 2020.2.4f1, 2021.1.0b6, 2021.2.0a4
Note:
1. Tested and reproduced the issue with InterlockedMin(), InterlockedMax(), InterlockedAdd(), InterlockedAnd() methods
2. Reproducible with Direct3D11, Direct3D12, Vulkan, OpenGLCore, OpenGLES2, OpenGLES3 Graphics API's
3. Errors:
"Shader Compiler IPC Exception: Terminating shader compiler process"
"Shader error in 'Hidden/Test': Internal error communicating with the shader compiler process"
"[Worker0] Shader compiler: Compile Hidden/Test - <Unnamed Pass>, Fragment Program: Internal error communicating with the shader compiler process. Please report a bug including this shader and the editor log."
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
- 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
Resolution Note (2021.2.X):
This is a crash in the 3rd party compiler we use. We cannot really do anything about it, unfortunately. As a workaround I would suggest doing the same in compute instead of a fragment shader.