Search Issue Tracker
Fixed
Fixed in 6000.0.10f1, 7000.0.0a1
Votes
0
Found in
6000.0.2f1
7000.0.0a1
Issue ID
UUM-71743
Regression
No
Closing the Lighting Window while Generating Lighting and having APVs in the Scene leads to a Memory Leak
How to reproduce:
- Create a URP 3D sample Project
- Add an Adaptive Probe Volume to the Scene
- Enable Adaptive Probe Volumes in the RP Asset (Light Probe System - Adaptive Probe Volumes)
- Navigate to Window > Rendering > Lighting > Adaptive Probe Volumes
- Generate Lighting
- Close the Lighting Window and observe the Console
Actual result: Memory Leak Error is logged, when the Lighting Generation is close to finishing, Console is flooded by "NullReferenceException: Object reference not set to an instance of an object." Errors until the Background Task for Lighting Generation is cancelled.
Expected result: No issues when Generating Lighting and closing the Window as the Background tasks are still in process.
Reproducible with: 6000.0.2f1
Couldn't test with: 2021.3.38f1, 2022.3.28f1, 2023.1.20f1, 2023.20f1
Reproduced on: Windows 11, macOS Sonoma M1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment