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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (2020.1.X):
This should be addressed at the GfxDevice API level