Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
2
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit's TextInput element does not inherit layout parameters from the TextField element when TextField.multiline is true
- The TileMap grid in the Tile Palette is not visible when Screen Space Ambient Occlusion is enabled
- Pressing “-” twice to remove a Tag in Project Settings > Tags and Layers throws errors in the Console window
- "State comes from an incompatible keyword space" error when clicking on a shader
- Test Runner's Player test fails when the IL2CPP scripting backend is selected
Add comment