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
- Text cursor remains visible when hovering over Command Line Arguments scrollbar in Unity Hub
- UI Builder’s "Background" icons for Repeat Y/X, Position X/Y and Slice Type are low quality and blurry in the Inspector window
- “X” button in Editor version search filter is difficult to see when Unity Hub theme is set to Dark
- [Android] The y-value of Input.mouseScrollDelta is positive when scrolling in both directions in the Player
- Crash on TexturesD3D11Base::SetTexture when using DirectX11
Add comment