how to enable TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp?

I've received multiple crash logs which spam until the user's game freezes

(Filename: C:\buildslave\unity\build\Runtime/Allocator/ThreadsafeLinearAllocator.cpp Line: 539)
Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 9)

hidden between hundreds of these lines lies another message

To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

I cannot for the life of me find out how to enable this thing, google wont give me any answers!
For anyone interested here are the crash logs as well:

one dude: https://pastebin.com/CcjPkuHj
other dude: https://pastebin.com/Ce0TL821

 

Same question. How know what a system have leak?

 

see this log in Xcode. Google tells me nothing either

 

Getting thousands of that errors since update to 2019.1

There is no such file where I can turn on that #define !!!
(Filename: ./Runtime/Allocator/ThreadsafeLinearAllocator.cpp Line: 541)

 

me too

 

Its been a few months and still can't find a solution!

 

Same here, it seems to not happen right when I start up Unity, but as soon as Unity runs for a while this nasty bug comes about. I am betting it is something internal to Unity where a job is not written correctly.

 

me too!

 

Got the same issue, using Unity 2019.2.1f1

Has anyone found a solution / workaround ?

 

This was a horrible problem for me and then I cleaned up how I was generating allocations and it went away. I think if your game throws a null error and doesn't shut down properly in the editor, that stuff will be left and leaky. So try restarting Unity first and check those TempJob allocations.

 

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

I removed all "Job", "Allocator", but the warning still exist.
I'm using 2018.4.7f1 Personal.

 

NavMeshBuilder.UpdateNavMeshDataAsync() is the reason about my issue. But I don't know how to fix it.

 

@fUring most definitely internal. You are gonna have to submit a report to Unity. They seem to be leaking garbage that way everywhere. Does it go away if you restart Unity?

 

I've restarted my Computer, but it still there. I'll submit a report soon. Thank you`

 

Still in 2019.2.3

 

Having same issue in 2019.2r5. Jut came out of seemingly nowhere. Opened bug with Unity and waiting to hear back. I can reproduce on a scene containing just a camera and directional light. Waiting to hear back from them. (The bug uploader would not for the project, so I had to zip it. Upgraded to the latest version of Post Processing and CORE, going to try the 2019.2.r6 that came out yesterday).

Error is :

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

Visually on more complex scenes where I see it, it looks like the UI is resizing itself between bigger and smaller.