Search Issue Tracker
Active
Votes
0
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Add comment