Search Issue Tracker
Fixed in 5.3.0
Votes
2
Found in
5.2.0b5
Issue ID
720254
Regression
No
[Crash][OcclusionCulling] Crash when entering visualization mode
Steps to reproduce:
1. Open attached project "OcclusionCullingCrash.zip"
2. Open scene "repro"
3. Select Main camera in hierarchy
4. In occlusion tab, select other than "Visualization" option and then select "Visualization" again
5. Unity should crash
Note: You might need to repeat step 4 for few times before unity crashes
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
DarthDisembowel
Nov 22, 2015 16:04
Oh, just noticed that it is fixed in 5.3.0. Never mind, I will check again when 5.3 is released.
DarthDisembowel
Nov 22, 2015 16:02
This bug is NOT fixed! I still have the same crash in 5.2.3.f1. This issue needs to be reopened.
Dave29483
Oct 05, 2015 09:43
I have this exact same issue on 5.2.1p2. As you say it takes a few tries of clicking say "Bake" then switching back to "Visualisation" to trigger it. It seems to be easier to trigger when in play mode.