Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
57
Found in
5.6.0f3
Issue ID
898262
Regression
No
JobTempAlloc error appears in Standalone Build output log if trees are in the Scene
Reproduction Steps:
1. Import attached project.
2. Open Test scene.
3. Build and Run.
4. In Standalone Build Data files, open output.log.
Expected result: Allocator errors should not be shown.
Actual result: The following error appears:
"Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak"
Note #1: If trees are removed from terrain, the error no longer appears.
Note #2: No obvious memory leak is detected.
Reproducible with: 5.5.3f1, 5.6.0f3, 2017.1.0p2
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
mushdevstudio
Jul 10, 2017 05:27
5.6.2p2 - still happening and is really killing performance.
kastus
Jul 06, 2017 21:24
5.6.2p2 - still happens
kastus
Jul 03, 2017 14:23
Version 5.6.2p1 - problem still exists.
PendingFox
Jun 26, 2017 12:28
it hit's GPU so much. and also I have no trees or terrain whatsoever. version 5.6.1f1
AntiSilence
Jun 21, 2017 23:03
I've also just noticed that I'm getting this issue, version 5.6.1f1
Xexyl
Jun 08, 2017 00:12
I found a case where a particle system can become corrupted in a way that causes this warning to spew every frame. I submitted a bug with very simple project where the problem happens 100% of the time, so hopefully that will help. Will update with the tracking number when it shows up on issue tracker. (no trees involved in this case)
jhunter22
Jun 07, 2017 12:36
Note: this is not just in win32 builds, any windows build (win64 confirmed)
I really don't get why Unity gives a 2017 beta prio over outstanding issues on the stable builds, they seem to greatly underestimate the impact of this bug.
GAMEDIA_Justin
May 30, 2017 15:24
This really hurts our performance and makes the output logs unreadable.
kalineh
May 24, 2017 01:27
We have this bug in 5.6.1p1 with no trees in our scene.
frankadimcosta
May 23, 2017 13:51
Unity 5.6.1p1 has this bug.