Fatal Error - Size overflow in allocator

Hi, I can build Tiny3D on preview 0.25, but when I try to do any changes to the scene or even just click on one of the game objects I get Fatal Error Size Overflow in Allocator. I would appreciate some help on how to solve this. Thanks!

 

Hello @Ted_Wikman,
Have same issue when trying to open ProjectTinySamples - TinyRacing. Using Unity 2019.3.13f1.
Steps to reproduse: Copy prject from repo -> Open project in unity -> Try to open scene "TinyRacing" (another way try to open/close DOTS Subscene in Hierarchy view) and i got same error as @cdorik.
Also same errors in other ProjectTinySamples.
UPD: Same issues on Unity 2019.3.14f1

 

I get the same error as well. Whenever I hit the Play button I get this fatal error.

 

Any luck figuring out a fix for this??

 

Any Tiny working project or package available. Suggest me best version of tiny project for unity 2019.3.13f1 or 2019.3.3f1

 

I tired with this sample project, followed to built \Assets\BuildConfigurations\Windows-DotNet.. Results me built error.. Attaching errors hereafter.

 

I received the same error, but not in Tiny, just normal DOTS. Loading my level1 scene would throw it and crash it. No idea how I fixed it, it just kinda started working again. I think it is being caused by one of the dependency packages. 2019.3.14f1 was my Unity version when I saw it. I think I have video footage of it on my Twitch stream... Showed up after I tried to do a build. (I still have not been able to get the build to work. It finishes with a success, but when I launch, it shows the Unity logo then hard crashes with no logs to go off of. Subscenes REALLY make building a PITA. Overall, I HATEEEEEEEE the subscene workflow. I just want Folders to organize)

 

I do not. I'm sorry. It gave me basically no information to go off of, then automagically fixed itself. I reviewed my stream as well, something weird happened where everything went white when I pressed play (after the build failed), then when I exited playmode, it threw the error. When I reopened Unity, it seemed to fix. I received it again later in the day (that was when trying to open the scene rather than on exiting playmode). I'm fairly sure it has something to do with subscenes.

 

Hello,

I have the same error by trying to follow this tuto on DOTS

I tried to use subscenes like in the video but same fatal error.
So I tried to delete the subscenes and use convertEntities and always fatal error !
What's strange is that I follow others tutos with 2019.3.5 and use convertEntities without problems
Here I use unity 2019.3.14f1 with this versions of packages :

 

Hey,I was test the mistake about size overflow in allocator,first i thought it was caused by the Prefab,but when i change the prefab or delete it,it still happened.The I thought the Project was created in the Universal Pender Pipline,maybe it was caused by the incompatibility of the SRP,so i change the material to the Built-In Render Pipeline with standard defult material,then it run well without error happen.Is that means the DOTS was still incompatibility with SRP??

 

I am using the Shader Graph generate the shader to create the Material,could it possible the incompatibility with the Shader Graph and DOTS?

 

I use shader graph and DOTS with URP just fine.

 

I have gone through the same error in 2020.1.1f.

I tried removing the "Temp" and "Library" folders in the project. After removing these folders I run the project and it creates new Temp and Library folders.

And it works...Initially, I thought that it will affect my work but it's working properly now.

 

For me it was a corrupt/obsolete asset I imported, deleting it directly through Windows (not inside Unity as it doesn't open) solved the problem.

 

Me too same problem on 2019.4.8

 

If you're on Windows try this:

Close the editor and any other open programs.

1. In Windows Explorer, right-click on the drive where your Unity installation is.
2. Select 'Properties'.
3. Select the 'Tools' tab.
4. In the 'Error Checking' section click on the 'Check' button.

Depending on your system you may get 1 or 2 different options.

Either way, scan your drive for errors and fix them.

Do the same after to the drive for your project if it happens to be on a different drive.

Try the editor / project again now.

Sometimes you may have corrupted data / sectors / etc.

 

I was getting the size overflow in allocator error. The editor log showed it crashing in a native multihashmap I was using for a physics spatial partition, however, I don't think that had anything to do with it.

It always happened on instantiating the same entity.

In the end it was an asset issue similar to the others. This is what I did:

1) Changed the mesh slightly in blender and re-exported the fbx (may or may not have been necessary)
2) Reimported (deleted old Unity metadata file manually)

This fixed it.