Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.0.0b19
Issue ID
662562
Regression
No
[ReflectionProbes] Changing resolution to an unsupported value causes OSX graphics system to crash
To Reproduce:
1. Open scene test in the project attached to the post (662544_reflection_probe_res_runtime) & play.
2. Change the field near 'Reload Scene with res' to a very high value, like 16384:
On OSX: Unity crashes, and osx either throws an 'graphics has crashed error' or Quartz crashes entirely and you're thrown to the login screen.
On Win: Unity freezes and memory usage starts to grow exponentially.
Also if you set resolution to some other value (like 1,2,4,8..4096), it seems to work fine, but since these value are not in the resolutions enum, the enum field in the inspector is empty. Maybe resolution should be changed into an int field in the editor (if some other values are supported) and it should throw an error when it's set to value which is to high?
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment