Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
1205072
Regression
No
[Metal] GfxDeviceMetal::CreateComputeProgram does not check inputs
The title is pretty explanatory, but due to a recent bug in compute kernel compilation, we ended up seeing some null shaders (size of source string is zero) from HDRP and crashing the Editor in the Metal driver. This happens because CreateComputeProgram is not checking the inputs and blindly subtracting the metadata size from the code size, which generates a very large size, and causes the Metal driver to access an invalid pointer.
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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
Resolution Note (2020.1.X):
This should be addressed at the GfxDevice API level