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
- NullReferenceException is thrown when selecting a Diffusion Profile
- Colliders of GameObject with Rigidbody component fail to collide with another GameObject when Rigidbody becomes Kinematic
- Shader cache uploads occur when the "Upload" parameter is disabled in the Cache Server settings
- "ApplySingleProperty clear overrides error" error when applying SerializedReference override to Prefab's nested Prefab
- About Unity window shows extended version numbers including staging tag
Resolution Note (2020.1.X):
This should be addressed at the GfxDevice API level