Search Issue Tracker
Not Reproducible
Not Reproducible in 2022.3.X
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
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.
Resolution Note (2022.3.X):
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.