Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X
Votes
0
Found in
2021.3.46f1
2022.3.52f1
6000.0.30f1
6000.1.0a7
Issue ID
UUM-90065
Regression
No
Increased Memory usage when Update Mode 'On Demand' Realtime lights are used and DX12 API is selected
Reproduction steps:
1. Open the attached “lights-memory-tests.zip” project
2. Open the “OutdoorsScene”
3. Build and Run the Project
4. After the Player is built, open Task Manager
5. Observe the Memory usage of the Player (lightsmemory.exe)
Expected result: The Player uses around 600 MB of memory
Actual result: The Player uses around 1.3 GB of memory
Reproducible with: 2021.3.46f1, 2022.3.52f1, 6000.0.30f1, 6000.1.0a7
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Pressing ‘Space’ on the keyboard calls “RequestShadowMapRendering()” on every light and pressing it a few times can increase the memory to up to 2 GB
- Does not seem to affect DX11 builds as the memory there stays under 600-700 MB
- In 2021.3 the memory usage was ~1.5 GB, 2022.3 ~1.4 GB, 6000.0 ~ 1.7 GB and 6000.1 ~1.7 GB
- The more Cube GameObjects there are in the Scene, the higher the memory usage is
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Packman: The same asset data is displayed differently in "Import" and "Remove" popups
- Reference to a deleted GameObject becomes "None" instead of "Missing" when the GameObject is restored with undo after entering and exiting Play Mode
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
- Blur shader doesn't work when the "Scene Color" Node is attached to the UI "Output" Node
Add comment