Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.2
2019.2.11f1
Issue ID
1196426
Regression
No
Memory leak in a specific built project causes the Player to eventually crash
How to reproduce:
1. Download the linked project 'Built Game.zip'
2. Launch the project (Ultra settings) with '-logFile Player.log' argument and open the generated log
3. Play the game for a while, walk into different rooms, interact with the world and constantly refresh the log
Expected result: No issues occur in the project
Actual result: An error regarding information about a possible leak is spammed in the generated log
Leak stack trace:
(Filename: C:\buildslave\unity\build\Runtime/Allocator/ThreadsafeLinearAllocator.cpp Line: 313)
Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 15)
0x00007FFE0BEFEFEC (UnityPlayer) StackWalker::GetCurrentCallstack
0x00007FFE0BF01DD9 (UnityPlayer) StackWalker::ShowCallstack
0x00007FFE0BEF1D48 (UnityPlayer) GetStacktrace
0x00007FFE0D0919DD (UnityPlayer) DebugStringToFile
0x00007FFE0BFAB1B8 (UnityPlayer) ThreadsafeLinearAllocator::Deallocate
0x00007FFE0C0637C1 (UnityPlayer) RenderNodeQueue::Reset
0x00007FFE0C05AE10 (UnityPlayer) RenderNodeQueue::~RenderNodeQueue
0x00007FFE0C06F179 (UnityPlayer) ShadowMapJobHeader::`vector deleting destructor'
0x00007FFE0BE6DC40 (UnityPlayer) JobDataGuardian::DecreaseRef<ShadowMapJobHeader>
0x00007FFE0C52EBE6 (UnityPlayer) JobQueue::Exec
0x00007FFE0C530E33 (UnityPlayer) JobQueue::ProcessJobs
0x00007FFE0C535993 (UnityPlayer) JobQueue::WorkLoop
0x00007FFE0C8593E4 (UnityPlayer) Thread::RunThreadWrapper
0x00007FFE6E817BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFE7002CED1 (ntdll) RtlUserThreadStart
Notes:
- Reproduced only once on a machine with these specs:
OS: Microsoft Windows 10 Enterprise 64-bit
CPU: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
RAM: 16GB
GPU: NVIDIA GeForce GTX 1060 GB
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment