Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0a3
2018.2.0b9
Issue ID
1056605
Regression
Yes
[Mac] Crash in Compute Shader where adding the same faulty code used to give an Error
Steps to reproduce:
1. Open user-attached project
2. Open file "00_LODBitonicSortingCS"
3. Add the following code right before "Data[DTid.x] = shared_data[GI];" (screenshot attached)
if (DTid.x >= 2050)
{
return;
}
Actual result: the shader code crashes upon recompiling
Expected result: an error is thrown like in pre-2018.1 versions (screenshot attached)
Reproduced with: 2018.1.0a3, 2018.1.1f1, 2018.2.0f1, 2018.3.0a4
Not reproduced with: 2017.1.1f1, 2017.4.7f1, 2018.1.0a2
Note: opening a project containing a file with the said code will either result the import process to crash (stack in the comments) or to freeze
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
Add comment