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.26f1
6000.1.0a3
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.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 (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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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 Window
After a couple of minutes after clicking play (and not interacting in any way), the Editor will just start spamming these warnings.