"Allocation of 32 bytes at 0000027D70016A00" error on Unity Editor

Recently a "Allocation " always happened on my Unity editor. Is that code problem or some other reason?




Unity Editor : 2019.3.06f

 

What is the entire text of the error? When does this happen? Does it occur when you run the project, when you do a specific thing, or just randomly?

Need more information.

 

A lot of same warning log "Allocation of 32 bytes at 0000029380026E90",end with a error "TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 512".




It is on Unity Editor without playing..

 

For me ,I could not any further apparently helpful information..

 

Have you recently built for iOS?

There is a bug out there that has this happening if you build for iOS:
https://issuetracker.unity3d.com/is...r-is-shown-after-building-the-project-for-ios

But it also says it was fixed.

Everyone basically says if they restart unity, or reopen their project, it goes away.

You may want to submit a bug on the issuetracker.

 

I was built on Windows.. Restart is helpful but temporarily.It will show up again just for a monent

 

I used some third-party plugin ,is those would be involved?

 

Could be... no idea, depends on the plugin.

 

Seen this happen on Windows

 

Just saw this on Unity 2019.4.7 in a project where I previously hadn't seen it. Restarted, message / warnings / errors were gone. Played, all looked good. Played again, Unity crashed. Started Unity again, played a few times. No crash.

Not very predictable. And the messages don't give me any useful hint on how I could debug this issue when it does occur. It does say re-compiling with a symbol enabled - but that's in a header-file that I don't think we can compile without Unity source code.

I had seen this occasionally in earlier versions of Unity, with a much larger project (that does not use ECS/DOTS/Jobs - at least not from my own code).

 

In my case, this apparently happens after doing builds.

 

Same thing for me on 2020.1. Happened after doing a windows build.

 

well things are getting worse than, it happened to me but in my case was after i starting adding LoadScene( ); in my project

 

It have just happened for me also, Unity 2020.1.7f1
After I "Build and Run" very simple android app
(I have also a LoadScene() in my little project), I don't know, if it is this, there is an bug with or not..

 

same thing happen at 2020.2.2f1

 

same thing at 2017.3.0p1 on windows, my game is built for android platform.

 

Still happening after building for android

 

I too am having this bug after I do builds on Windows. Unity V 2022.2.1f1

looking on reddit apparently this is a solve to a similar issue in the past https://www.reddit.com/r/Unity3D/comments/75syxl/solved_tls_allocator_alloc_temp_thread_underlying/

Has anyone tried reimporting all of your assets?

 

Yes, this did solve the issue for me in the past. I occasionally clean up my Library folder, keeping only the files I need for configuration and deleting everything else so that Unity recreates it. Depending on the number of shaders that you use, this may significantly increase the build time on the next build which will re-create the shader cache. But it may also significantly reduce the storage space that your project needs (if you've gone through a number of Unity versions with the project).

 

Just hear to chime in that Im getting this issue this week 2020.3.8 LTS. I reported it on the bug tracker as well.

The string thing is I've been using Unity for the past few months and it didn't start happening until this week. Ive been learning to do unit testing and it only happens when I run the test suite. As if encouraging devs to test wasn't hard enough, we have to fight bugs along the way

 

Happens in the editor on each editor frame. Without building or anything just opening the scene. 2020.3.11f1

 

Happens to me using Unity 2021.1

I was working around Android.

I reimport Assets and looks gone

 

it still happening on 2020.2.2f it always happen and it make a Unity freeze and error sometime

 

Same happens to me when doing a linux server build, Unity 2020.3.1f1

 

I have exactly this on 2021.1.27f1. Have reimported multiple times but it only helps temporarily. VERY irritating.

 

This is still happening in 2021.2.4f1 - is anyone from Unity reading this ?

 

Still irritating in 2020.3.21f1

 

This is still happening in 2021.1.15f1

 

Very similar / same issue in Unity 2021.2.5f1

 

I've submitted a bug report - 1384157 - the problem is that this is literally ALL the info the editor gives you. Just having more info would be a useful change.

 

Can I recommend that more debug information is added to this error message? That would help more than trying to reproduce it on a project where even when I'm developing, I can go for days without this issue appearing.

 

I'm not the only person having this issue. And like I said: It comes and goes. As soon as I find a way to reproduce it somewhat reliably, I'll submit a project. At the moment, all I can say is that it appears to happen mostly, maybe exlusively, in some relation ot (Unity, standard) terrain. I know it's damn little to go on. That's why I asked if it were possible to give a more helpful error message. I know from my own games that when the error I see in the Unity dashboard or the player log is essentially "null reference exception", that's near impossible to track down. Good error and exception messages is the #1 take-away I took from my current project, where the simple change of making sure every assert has a unique message made my life 100 times easier.

 

I have the same issue.
And the problem came when I started using terrain. As long as I was using cube or plane, it was fine. If I modify the terrain, the error comes sooner. If I turn off the terrain [enable = false], the error doesn't seem to appear.
Unity 2021.2.6f1, Ubuntu 21.04, i3wm,.

EDIT: similar message directly in the error log -> TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 13328

 

Same issue, Unity 2021.2.4f1, Happened at the exact time I added a new layer on the terrain, it had 4 previous layers, when I added the new one, it says Allocation of 56 bytes at ... and whenever I do anything on the editor it says Application.UpdateScene for a few seconds

 

I guess MelvMay's request was for not...

Listen guys... I don't necessarily know Unity's internal process (Melvmay would know more).

But I've worked in enterprise software for 15 years. And I will say this "me too" thread is useless from a QA perspective. It's why I suggested issuing a bug report almost 2 years ago. And I've received the notifications every so often someone "me too"s this thread.

With the nature of how bug testing works, what has been given in this thread just isn't going to cut it. If it did, it would have been resolved by now. But it's not.

It's not like QA enjoys having bugs out there. That looks bad for them.

But if they can't recreate, or have any substantial way to look into things, there's nothing they can do.

And like Melvmay has stated, the error message you're getting isn't enough info to go on.

There's talk about better error reporting... but the thing is, that's what the bug report is!

It contains more than just the error message. I don't necessarily know what is in Unity's bug report... but usually it contains a many things like a dump of the memory, including the call stack, and log files, and more. All of that information is how QA and engineers hunt down these problems.

The comments about what you were doing just before the crash is also very helpful. And that's why the bug reports usually have a field for user comments. Put that info there.

But without that... this thread is going to be for not.

 

Just FWIW: It's not a crash bug. It leads to a dramatic slow-down of the editor, but not to a crash. If I can reproduce this issue in a project that's not 30+ GB I'll send in a bug report. Right now I prefer to not clog up my uplink for half a day.

Meanwhile, I'll try to give as much useful information about when and under what circumstances it happens, and how often, etc. - because as I said, even on a project where it does happen again and again, I can go for DAYS without this issue showing up.

 

The error joacoremis has, but in Unity 2021.2.5f1 Windows.

1. Create new project (build-in rendering pipeline).
2. Add terrain to scene.
3. Add 5 or 6 layers to the terrain (I used 32x32 textures and made no changes to terrain)
4. Press play
5. Stop it.

Observe error and warning spam starting in console...
- TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 48160
- Internal: Stack allocator ALLOC_TEMP_MAIN has unfreed allocations, size 48160

You have to have Terrain object selected for it to happen.

 

I have the same issue. When the problem appears, I see a massive increase of the script in the profiler.
The profiler says: PostLateUpdate.MemoryFrameMaintenance = 80ms
It's getting slow, because it writes in the Console. Maybe that leads closer to a solution.

 

@MelvMay Calm down. I'll be submitting the bug, I've submitted plenty over my 10+ years using Unity, once my ISP functions properly again. They had lightning damage on towers so I can not submit without getting an "Unabled to write" error from the Bug Reporter (I suspect it is cause my internet drops every few minutes).

In meanwhile I left these instructions so that anyone else running into this knows why it happens, assuming they are using Terrain, and how to avoid it until a fix comes along (that is, don't use more than 4 textures on Terrain).

 

Leslie-Young, you're a hero for finding out about the 4 textures on the terrain!!! That's 100% it.
I submitted a bugreport: https://fogbugz.unity3d.com/default.asp?1389106_10irvqj2041soud7
I also found out that this bug does not appear on 2021.2.0f16, so it might have been introduced after the beta was concluded.

Aside from all this, I'd like to mention that MelvMay's posts appeared passive agressive to me and not helpful in the overall process of this bug hunt. Writing "I just can't...." feels toxic to me and I don't see the benefit to the conversation to it. It's made worse by the fact that it's written by a unity staff.

Thank you very much to everyone posting and getting me closer to being able to post a bugreport including a project for easy reproduction! ♥

 

As someone who has worked as a developer behind the scenes in enterprise software along side QA for 15 years.... I just can't.

When people are told "if you want to get this resolved, the path to doing so requires information that is submitted via the bug report" and other's going "no"... is also toxic. Hence the aggravation.

I'm happy you submitted a bug report. But that doesn't mean 2 years of "me too" hadn't occurred.

If you came into a room full of people shirtless complaining about the cold, you wouldn't say to the guy telling everyone to put on a shirt "god, you're so toxic, I put on a shirt" while other's are still not wearing shirts.

So yeah... I just can't with this thread anymore after going on 2 years.

Thankfully a more substantial bug report was submitted. Thank you for that.