Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.3.42f1
Issue ID
UUM-82957
Regression
No
Crash on Light::SetupHalo when exiting Play Mode
How to reproduce:
1. Open the user project
2. Open the user Scene
3. Enter Play Mode
4. Exit Play Mode
Reproducible with: 2022.3.42f1
Reproducible on: Windows 10 (reported by user)
Not reproducible on: No other environment tested
Note: Not reproducible by CQA and project not provided by user
First few lines of the stack trace:
0x00007ff63a5f6372 (Unity) Light::SetupHalo
0x00007ff63a6a28d8 (Unity) RenderSettings::UpdateGlobalState
0x00007ff63a97d14f (Unity) CallbackArray2<Camera & __ptr64,Camera & __ptr64>::Invoke
0x00007ff63a97e916 (Unity) RuntimeSceneManager::SetActiveScene
0x00007ff63bbe8e7b (Unity) EditorSceneManager::SetActiveScene
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
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Resolution Note:
I'm happy to hear that our user has resolved the problem by removing some faulty/incomplete materials and shaders from the project.
But on our side, in order to reproduce and fix the issue (by potentially adding some guards) we need access to the files that were causing this problem, ideally in a minimal repro project.