Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.X, 6000.6.X
Votes
6
Found in
6000.0.66f1
6000.3.4f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-132677
Regression
No
Editor memory leak when entering and exiting Play Mode in a blank URP project
How to reproduce:
1. Create a new 3D URP Project
2. Install the Memory Profiler package
3. Enter Play Mode, capture a Memory Profiler snapshot or note
4. Exit Play Mode
5. Enter Play Mode again, capture another Memory Profiler snapshot
6. Observe the allocated memory difference between the two snapshots
Actual result: Memory leaks ~20-40mb each time Play Mode is entered
Expected result: Memory usage is stable between Play Mode sessions
Reproducible in: 2023.1.0a1, 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Reproducible on: Windows 11, macOS 15.3 (M2 Ultra)
Not reproducible on: No other environments tested
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
TeorikDeli
Feb 11, 2026 12:38
I think this is not only happening when enter-exit play mode. We have memory leak problem in two different project (6000.0.66f1, 6000.3.5f2). Unity can easily use 20-40 GB (yeah, GB) memory when I check from the Activity Memory. We're periodically reopening Unity because of this problem.