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
- Variant Family window UI issues when Prefab title is long
- Player crash when switching focus in Exclusive Fullscreen mode with DirectX 12
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
Add comment