Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
4
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a1
6000.5.0a1
Issue ID
UUM-120234
Regression
No
Memory leak when entering and exiting Playmode repeatedly
Steps to reproduce:
1. Create and open a new project
2. Open Windows task manager
3. Observe the current Unity project memory usage in task manager
4. Enter Playmode
5. Exit Playmode
6. Observe the current Unity project memory usage in task manager
Expected result: Memory usage displayed in the task manager stays the same
Actual result: Memory usage displayed in the task manager jumps on average by 4 MB
Reproducible with: 2023.1.0a1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Repeating steps 3 to 6, memory usage keeps climbing in the task manager. After ten minutes of this process, memory usage jumps by about 1 GB
Comments (1)
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
ddooms
Mar 17, 2026 18:07
Still happening in 6000.3.11f1 as of 3/11/2026. Ridiculous. Happens on every domain reload too