Debug Stack Leak?? How To Fix It?

hello i've been working in unity, and suddenly last night i got a random froze and i started getting this error. it does nothing, except it stops the IA from running, sort of. i looked into in it in google but it only appears in older unity versions as a possible bug. Any idea what causes it? or how to fix it?.


Internal: Stack allocator ALLOC_TEMP_THREAD has unfreed allocations, size 390
DEBUG_STACK_LEAK in StackAllocator.h. This will output the callstacks of the leaked allocations

 

I followed what google said and just ignored it until it dissapeared.
Two or three days after it appeared it just dissapeared, i dont really remember if i changed something or just went away on his own. sorry.

 

We have this same issue, after changing from .net3 -> .net4

we are using Unity 2018.4.4 LTS

 

We're getting similar errors and warnings:

⯃ Expanding invalid MinMaxAABB

⯃ Converting invalid MinMaxAABB

⚠ Internal: Stack allocator ALLOC_TEMP_THREAD has unfreed allocations, size -131928686

⚠ To Debug, enable the define: DEBUG_STACK_LEAK in StackAllocator.h. This will output the callstacks of the leaked allocations

We have tracked down the issue, and in our case it is caused by a particle sub emitter having too low of a Max Particles setting. A bug report with minimal repro has been sent to Unity.

If you have the same issue, try increasing the Max Particles setting of any particle sub emitters.

We have reproduced the issue in:
2018.4.7f1
2018.4.9f1
2019.1.14f1

It doesn't reproduce in:
2019.2.6f1

 

Just got a reply from Unity. It's a know issue, and progress on it is tracked over here:
https://issuetracker.unity3d.com/is...awning-particles-with-world-collision-enabled

 

I got this issue fixed in my project when:
1- Reimported all the assets(Assets>Reimport All)
2- Cleaned all the Console Warnings (Console>Clear)
3- Then I just hit Play.
-Unity Version: 2020.2.1f1
Hope it helps

 

this fixed it for me, just started a new project with limited code and objects.

 

This good old one is back in 2021.2.8f1 <3 even in a empty scene..
Clearly i got a memory issue, since the its only running the console spasm when unity editor is selected active, if i select outside the editor it stops until i come back to it.

 

i can confirm the same in 2020.3.23f1. Even in an empty scene it gives these console spams; the suggestion above with reimporting sadly didn't work.

 

Oh look, I went looking for a solution and came across this page.

I've reimported all, and even deleted the whole library just to make sure. Just endless amounts of console spam.

 

I can confirm that this bug (DEBUG_STACK_LEAK in StackAllocator.h) is still here in version of Unity 2020.3.27f1 Personal.

 

Hello,

I have send bug report. In the screenshot attached you can see, what happened in the Console Tab. I suspect this happen when downloading new larger assets from Unity store, because it don't happen when downloading smaller assets. Today's was 4,4 Gb. It didn't happened when I was downloading today the other asset which is 590 Mb big. This bug was first intruduced in this version of Unity 2020.3.27f1 as I'm aware off.

 

Got this bug today. I was being a silly and doing something like this (I typed the function name wrong):

Code (CSharp):

1. void Start()
2. {
3.    TestLog();
4. }
5.  
6. void TestLog()
7. {
8.    UnityEngine.Debug.Log("Test");
9.    TestLog();
10. }

Hope this helps someone...