Search Issue Tracker
Not Reproducible
Votes
1
Found in
6000.0.60f1
Issue ID
UUM-123113
Regression
Yes
Memory leak occurs when focused on Player while using Direct3D12
How to reproduce:
1. Open the attached “IN-121512” project
2. Open the SampleScene
3. Build and Run the project
4. After the Player is built, open the Task Manager
5. Keep the mouse focused on the Player
6. Observe the result
Expected result: Memory remains stable
Actual result: Memory consistently increases
Reproducible with: 6000.0.60f1
Not reproducible with: 6000.0.46f1
Reproduced on: Windows 11 (reporters machine)
Not reproduced on: No other environment tested
Notes:
- Not reproduced by CQA
- The issue does not occur when using DX11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
We fixed a memory leak in d3d12 and it will land on 6000.0.62f1, but we couldn't observe such leak in this case.
It's expected that memory usage increases for certain amount when using d3d12. After that it'll be stable.
If the memory usage does increase without stopping, please check 6000.0.62f1 when it's available and report again if the issue persists.