Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3
2019.3.0f5
2020.1
Issue ID
1214846
Regression
No
[DXR] GPU Memory leak when building RayTracingAccelerationStructure
How to reproduce:
1. Download "DXRMemoyLeak.zip" project
2. Set Graphics API to DirectX12
3. Enter the PlayMode -> select "DXRTest" GameObject
4. Open a memory profiler tool (E.g. GPU Z)
5. In Inspector Window select "Recreate All" -> look at the memory profiler tool "Memory used" line
Expected result: No memory leak when building RayTracingAccelerationStructure
Actual result: Memory leak when building RayTracingAccelerationStructure
Reproducible in: 2019.3.1f1, 2020.1.0a22
Could not test with - 2019.2.20f1 and earlier (no DXR)
Notes:
- The average leak is about 150 MB, by clicking "Recreate All" more times - this can build up to 3000 MB leaked memory
- If "Recreate Acceleration Structure" is clicked after "Recreate Mesh", it rebuilds RayTracingAccelerationStructure and leaks memory
- Whenever "Recreate Mesh" is clicked, it recreates the mesh without memory leak
- "Recreate All Same Mesh Ptr" recreates the mesh in the same pointer and builds RayTracingAccelerationStructure without memory leak
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 (fix version 2020.1):
2020.1.0a24
Resolution Note (fix version 2019.3):
2019.3.6f1