Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.2p4
Issue ID
771448
Regression
Yes
[Regression][5.3] 'Threadsafe Linear allocator' error is thrown when opening new project in 5.3.2p4
Steps to repro:
1. Open Unity 5.4.0p4;
2. Create new empty project;
3. Observe console.
Actual result:
'Threadsafe Linear allocator (Job temp alloc) has allocations that are more that 2 frames old - this is not allowed and likely a leak'
error is shown when starting/opening new project in Unity 5.3.2p4.
Regression introduced 5.3.2p4.
Expected result:
Allocator errors should not be shown after creating/opening new project.
Notes:
- Happens on Windows 10 (stably);
- On OSX happens when launching Unity only for the first time;
- Reproducible in: 5.3.2p4;
- Not reproducible in 5.3.2f1, 5.3.1f1, 5.4.0b7;
- Issue also reproduces when sculpting terrain (painting height) - in this case, allocator errors are constantly spawned.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment