Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a2
2019.2.0a1
2019.2.6f1
2019.3.0a1
2020.1.0a1
Issue ID
1187844
Regression
Yes
"Internal error communicating with the shader compiler process." error is thrown when inlined computation is used in a Shader
How to reproduce:
1. Open user-submitted project (ShaderCompilationCrash)
2. Reimport the asset Shaders/FxTerrainLevelBuildMatch.compute
Expected result: the shader compiles without any errors
Actual result: "Compiling CSMatchResolve: Internal error communicating with the shader compiler process" error is thrown
Reproducible with: 2019.1.0a2, 2019.1.14f1, 2019.2.8f1, 2018.3.0b5, 2020.1.0a7
Not reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.1.0a1
-
t5impact
Jul 28, 2020 14:09
I am also having this error 2019.3.0f3. Is there any way to alleviate this issue, and if so, how?
-
kmcclary
May 08, 2020 18:55
I'm having this error in 2019.3.9f1 . How do I remove the debug pragma?
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
- [Hub] Editor is shown in the "Installing" state indefinitely when the installation fails due to INVALID_DESTINATION error
- Searching packages on an ill-configured scoped registry targeting Google Unity API registry throws an error
- Not possible to deduce the source of 'Shader properties can't be added to this global property sheet.' error
- [MacOS] Mouse input gets interrupted when changing values in inspector by dragging mouse
- Adding/removing components expands collapsed components view in the Inspector window
Resolution Note:
This error message indicates that the shader compiler process has crashed. Often it is something in our code in which case we can fix things. However, in this particular case the crash happens in the D3D compiler which is a black box to us.
This case looks like a regression due to change we made in 2019.1, adding D3D10_SHADER_SKIP_OPTIMIZATION compiler flag when #pragma enable_d3d11_debug_symbols is used, to produce saner debug shaders. Unfortunately this flag seems to cause the compiler crash with this particular shader content.
So the easy workaround here is to remove the debug pragma. If the debug symbols are needed then the only way is to refactor the shader until the crash is gone.