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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (2020.1.X):
This should be addressed at the GfxDevice API level