Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.2.0b6
Issue ID
UUM-53662
Regression
Yes
Memory usage steadily increases when there are two Bloom effects active
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:
* Exiting the Play Mode does not release the used memory
* In the 2023.2.0b4-2023.2.0b6 versions, the increase in memory usage is the most visible
* Starting from 2023.2.0b7 the memory usage increase is not so drastic and the overall usage fluctuates and is unstable
Comments (1)
-
Jack_Eatock
Dec 02, 2024 21:25
I had the same issue in 2022.3.9f1, which was fixed when I updated to 2022.3.53f1
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note:
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.