Search Issue Tracker
By Design
Votes
0
Found in
2022.3.11f1
2023.1.17f1
Issue ID
UUM-56537
Regression
No
Custom Render Pass increases memory usage when in Play Mode
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/Empty.unity” Scene
3. Enter the Play Mode
4. Observe memory usage with Task Manager or another app
Expected result: Memory usage stops increasing when in Play Mode and releases after exiting
Actual result: Memory usage increases when in Play Mode and does not release after exiting the Play Mode
Reproducible with: 2022.3.11f1, 2023.1.17f1, 2023.2.0b13, 2023.2.2f1, 2023.3.a15
Could not test with: 2021.3.32f1 (Assets\Shaders\KawaseBlur\KawaseBlur.cs(160,26): error CS0115: 'KawaseBlur.SetupRenderPasses(ScriptableRenderer, in RenderingData)': no suitable method found to override)
Reproducible on: Windows 10 Enterprise 21H2, Mac M1 Pro
Not reproducible on: No other environment tested
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:
BlurredLayerTextureScriptableFeature's OnCameraCleanup(CommandBuffer cmd) function sets RTHandles to null without releasing them causing the memory leak