Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2022.3.5f1
2023.2.0b4
2023.3.0a1
Issue ID
UUM-45889
Regression
Yes
Progressive Lightmapper leaks memory and often never finishes in scenes with Probe Volumes
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/SampleSceneAssets/Scenes/SampleScene.unity” Scene
3. Open the Lighting window (Window > Rendering > Lighting)
4. Press “Generate Lighting”
Expected result: Lighting is generated
Actual result: The project is stuck on loading Global Illumination and errors about memory leaks are seen in the Console window
Reproducible with: 2022.2.0b4, 2022.3.5f1, 2023.1.0a19
Not reproducible with: 2021.3.28f1, 2022.1.24f1, 2023.2.0a23
Could not test with: 2022.2.0a1, 2022.2.0b3 (crashes when opening the project)
Fixed in: 2023.1.0a20
Reproduces on: Windows 10 Enterprise 21H2
Notes:
- Warnings about leaked memory are shown in the Console window “Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak”, ”To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.”
- The Lightmapper stops working when Probe Volumes are enabled, or even when there is just a Probe Volume component in the scene regardless of whether they are enabled in the settings. As soon as you start to generate lighting memory leak warnings will constantly start showing up in the Console and the progress bar will show up in the bottom right but never go above 0%, even after hours of waiting
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
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- 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
Resolution Note:
The GI baking works as designed but some patience is required when using the experimental version of Probe Volumes in 2022.x. GI baking takes a long time to complete because the light probe sample multiplier is set to 100. This means that for indirect lighting for instance, each of the 73406 probes take 1024000 samples. GPU utilization for the compute queues in task manager can show you that the GPU is still busy. Progress reporting for APV probes isn't visible in 2022.3 but this is much better in Unity 2023.x where the feature isn't experimental.
Resolution Note (2023.3.X):
The GI baking works as designed but some patience is required when using the experimental version of Probe Volumes in 2022.x. GI baking takes a long time to complete because the light probe sample multiplier is set to 100. This means that for indirect lighting for instance, each of the 73406 probes take 1024000 samples. GPU utilization for the compute queues in task manager can show you that the GPU is still busy. Progress reporting for APV probes isn't visible in 2022.3 but this is much better in Unity 2023.x where the feature isn't experimental.