Search Issue Tracker
Fixed
Fixed in 2023.1.11f1, 2023.2.0b7, 2023.3.0a1, 2024.1.0a1
Votes
1
Found in
2023.1.4f1
2023.2.0a20
2023.3.0a1
2024.1.0a1
Issue ID
UUM-41988
Regression
Yes
Light Probe GPU memory is not deallocated when cancelling a bake
Steps to reproduce:
# Open any scene
# Open the Task Manager and view your GPU memory utilization
# Add some probes
# Crank the lighting settings (such as probe multiplier) to make the allocation sizeable (depending on your GPU).
# Make sure you're using the GPU Lightmapper
# Hit 'generate lighting'
# Wait until you see the VRAM allocation happening (should be a steep hump in the video memory utilization)
# Allow the bake to finish (see that the memory is indeed deallocated)
# Initiate another bake
# This time, before the `Baking` step is done, but after the allocation has finished, hit `Cancel` in the Lighting Window.
# Notice how the memory is not cleaned up.
# Hitting `Generate Lighting` again will allocate even more memory.
# Repeat generate-cancel as many times as you see fit, it will keep stacking memory.
Notes: The LightBaker process is properly cleaned up. This reproduces only with LightBaker and LightProbes in 2023.2 and 2023.1. It also affects APV.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment