Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
1
Found in
2022.2.13f1
2022.2.21f1
Issue ID
UUM-36008
Regression
Yes
[Burst Occlusion Culling] Editor Crash when occlusion enabled and enter / exit playmode
Steps
- open project " BOC_editor_crash_OnDispose "
- open SampleScene
- enter playmode
- exit playmode
Expected: no crash
Actual: crash
Repro: 2022.2.13f1, 2022.2.19f1 on MacOS
No repro: 2022.2.12f1, 2022.2.11f1 on MacOS
NOTE:
- used Entities Graphics 1.0.8 which is not available in package manager for these versions
- not 100% repro rate - may require a few attempts of enter / exit playmode
- “SampleScene 1” also repros the crash but has lots of errors in console in 2022.2.13f1 - so for this bug better to use the basic scene “SampleScene”
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug as we won't be supporting Burst Occlusion Culling bugs in this experimental version and future plans may solve the problem.
Today we will be closing this case. Thank you again for taking the time to report this issue.
Resolution Note (2022.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug as we won't be supporting Burst Occlusion Culling bugs in this experimental version and future plans may solve the problem.
Today we will be closing this case. Thank you again for taking the time to report this issue.