Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0a4
Issue ID
747880
Regression
Yes
[GL][ES] Crash on compute shader use
Steps to reproduce:
1. Download attached project "repro_747880.zip"
2. Open it via console with launch parameter "-force-glcore45"
3. Play "New Scene"
4. Observe that Unity editor has crashed
Expected result: Not crashing
Note: Disabling "Ignore culling" option does not crash Unity, but no shader can be seen either.
Does not seem to reproducible before 5.4
Everything works as expected with standard configuration (no launch parameters) using DX11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment