This error keeps appearing in my console after few seconds, even if I clear the console:
TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations
My scene playmode and pause mode are off, still. What could be causing this?
Edit → Preferences → GI Cache → and Clean Cache
I solved this error. You must change .Net option in Player Setting from .Net 3.5 to .Net 4.6.
for me, restarting the editor fixed the problem 
Disabling Project Settings → Player → Other Settings → GPU Skinning and Graphics Jobs
seems to have worked for me in Unity 2019-3.3.
Hi Sisters and Brothers,
I have the same issue with my really first game.
I use Unity 5.5.0f3 (Windows 8.1 64 bits) / Visual Studio 2015 Update 3.
I have instantiated (Standard Assets/PartcileSystems/Prefabs) Fireworks several times in my scene.
The sequence to get the error in the console of the Unity editor, is when I select the one of the Fireworks game object.
As soon as, I select another game object (which is not a Fireworks), the error stops to loop, but the error is displayed only once. If, I select a Fireworks game object, the error message loops in the console infinitively.
So to be sure that this comes from Fireworks game object, I’ve created a new project, I have created a Fireworks objects, and this error appears in the console. So, this may come from this asset !?
In my case, the root cause was with the Event Manager. It tried to match its mouse wheel event (vector 2) to my input system’s mouse action which (in my case) only outputs the y axis (float). After unchecking the mouse wheel event in the Event Manager, the error disappeared.
Just had this happen to me when attempting to make a new build (Unity 2019.4.25).
Tried wiping the library, GI cache and a bunch of other ideas, none worked.
I then sorted it out by simply reloading my unity window layout.
Might be worth a try if you’re about to commit to a long library reimport session.
Cheers
I had this problem too, when it happen it will make my Editor crashed and close by itself
I don’t know why But it always happen if I publish my edited thing by collaborate.
Experiencing this in 2022.3.22f1. Seems to be specifically related to moving my cursor in and out of the scene view when not in play mode. Unsure if related, but it began after I accidentally caused a memory leak and persisted after I resolved the issue. Only solution seems to be restarting the editor.