Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.3.0b5
Issue ID
1090797
Regression
No
Compute shader error crashes Unity shader compiler
How to reproduce:
1. Open the "Compiler Crash.zip" project
2. Check the console for errors
Actual result: Compiler crashes.
Reproducible with: 2019.1.0a13, 2018.3.1f1, 2018.2.20f1, 2018.1.9f2, 2017.4.17f1.
Notes:
The crash on the compiler is caused by lines "for (int i = 0; triTable[cubeIndex][i] != -1 && i < 16; i += 3)", KeelTheCompiler.compute: 129. and "triangleRW.Append(t);", KeelTheCompiler.compute: 152. Removing "triTable[cubeIndex][i] != -1 &&" from the loop OR removing "triangleRW.Append(t)" line fixes the error.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
minor/cosmetic