Search Issue Tracker
Fixed in 2022.2.19f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a13
Votes
2
Found in
2022.2.12f1
2023.1.0b9
2023.2.0a8
Issue ID
UUM-31709
Regression
Yes
[DXR] GPU memory leaks when Renderer.rayTracingMode is set to UnityEngine.Experimental.Rendering.RayTracingMode.DynamicGeometry
Reproduction steps:
1. Open the attached project “RayTracingLeak”
2. Open “Assets/OutdoorsScene.unity”
3. Enter the Play Mode
4. In the Hierarchy window select “ObjectSpawner” GameObject
5. In the Inspector window, change the “Ray Tracing Mode” property value to “Dynamic Geometry”
6. Open Task Manager
7. Focus the Editor and observe memory usage in Task Manager
Expected result: Memory usage slightly changes and settles
Actual result: Memory usage keeps increasing
Reproducible with: 2022.2.0a15, 2022.2.12f1, 2023.1.0b9, 2023.2.0a8
Not reproducible with: 2021.3.21f1, 2022.2.0a14
Couldn't test with: 2020.3.46f1 (Assets\SpawnObject.cs(23,37): error CS1061: 'Stack<GameObject>' does not contain a definition for 'TryPeek')
Reproducible on: Windows 10
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
Add comment