Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. In this specific case, the workaround is to update to the 23.3 version since the issue is fixed there. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/_Scenes/demo_test_2.unity” Scene
3. In the Hierarchy Window, select “_EFFECTS > IE_Main” GameObject
4. In the Inspector Window, enable the Bloom effect “Volume > Bloom”
5. Open Task Manager (or Activity Monitor)
6. Enter the Play Mode
7. In the Task Manager, observe the Unity process
Expected result: The Unity process’s memory usage remains stable
Actual result: The Unity process’s memory usage steadily rockets
Reproducible with: 2023.2.0b4, 2023.2.0b15, 2023.3.0a8
Not reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.2.0a1
Fixed in: 2023.3.0a9
Could not test with: 2023.1.15f1, 2023.2.0a2 - 2023.2.0b3 (Game View is dark with only UI visible and the Console Window is spawned with warnings and errors)
Reproducible on: Intel macOS 13.5
Not reproducible on: No other environment tested
Notes:
Issues you vote on will appear here