Search Issue Tracker
Fixed
Fixed in 6000.0.71f1, 6000.3.12f1, 6000.5.0a9, 6000.6.0a1
Votes
2
Found in
6000.0.26f1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-86868
Regression
No
A memory leak occurs when selecting the Console Window and the Inspector Window covers the Game View Window when specific UI elements are displayed in it
Reproduction steps:
1. Open the “ASDQWE” project
2. Open the “Battle Corridor.unity” Scene
3. Enter the Play Mode
4. In the Game View click on the little "character" icon left to the backpack in the toolbar
5. Click on the Inspector Window
6. Click the Console Window and observe it
Expected result: No errors or warnings are thrown
Actual result: “Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak” warning and other memory leak warnings are infinitely thrown
Reproducible with: 6000.0.26f1, 6000.1.0a3
Not reproducible with: 2021.3.46f1, 2022.3.52f1 (Multiple compilation errors)
Reproducible on: MacOS 14.6.1 Intel, M3 (user’s)
Not reproducible on: No other environment tested
Workaround: Have both Inspector and Game View Windows visible
Notes:
- The issue occurs regardless of whether anything is selected in the Inspector Window or not
- The warnings are thrown when hovering over any UI elements
- The warnings are only thrown when the Inspector Window covers the Game View Window
- The user stated that the Editor crashes when launching it with the “-diag-job-temp-memory-leak-validation” flag but CQA could not reproduce this behavior
The user-experienced crash’s first few lines of the stack trace:
{noformat}#0 0x000001051171f8 in ThreadsafeLinearAllocator<true>::PrintBlockAllocations(int, int)
#1 0x0000010511a0f4 in ThreadsafeLinearAllocator<true>::FrameMaintenance(bool)
#2 0x000001051025e4 in MemoryManager::FrameMaintenance(bool)
#3 0x000001055528dc in InitPlayerLoopCallbacks()::PostLateUpdateMemoryFrameMaintenanceRegistrator::Forward()
#4 0x000001055125d8 in ExecutePlayerLoop(NativePlayerLoopSystem*){noformat}
Comments (2)
-
Paul-Swanson
Mar 21, 2026 04:03
Reproduces in 6000.3.9f1 during Play mode with UI Toolkit (UGUI-free project). Memory climbs continuously from first frame, reaches critical levels within minutes — process required force kill. Project uses dynamic VisualElement creation/removal (toast notifications via StartCoroutine + RemoveFromHierarchy). Reverting all dynamic element changes stabilized memory at expected levels, confirming the engine is retaining references to detached VisualElements.
Bug identified with assistance from Claude Code. Was attempting to create a Toast limiter on screen before runaway memory consumption
-
Tulrath
Nov 19, 2025 01:11
Reproducible in 6000.2.6f2 with no window or tab interaction needed.
- The issue occurs regardless of whether anything is selected in the Inspector Window or not
- The issue occurs with or without UI Elements shown or interacted with
- The issue occurs no matter the position or coverage of the Inspector Window or the Game View WindowAfter a couple of minutes after clicking play (and not interacting in any way), the Editor will just start spamming these warnings.
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.3.12f1):
Fixed in 6000.3.12f1
Resolution Note (fix version 6000.0.71f1):
Fixed in 6000.0.71f1