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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2020.1.X):
This should be addressed at the GfxDevice API level