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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment