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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
ohbado
Sep 03, 2017 09:25
Still happens in 5.6.3p2.
MikeHergaarden
Aug 30, 2017 11:14
FYI: 2017.1.0p5 claims to have fixed this, will take me a few days before I can confirm this.
https://unity3d.com/unity/qa/patch-releases/2017.1.0p5
ThomasEgan
Aug 30, 2017 03:10
Still occurs in 5.6.3p1
Sir-Travisty
Aug 29, 2017 22:27
Still occurs in 2017.1.0f3 with Timeline and Audio tracks, if the audio asset is inactive when starting the editor.
piger91
Aug 29, 2017 10:01
i get the issue while controling my Animations ,but it doesn't link to any script,what the hell is it? how can i fix it?
ionside
Aug 26, 2017 06:00
Still having this issue in 2017.1.0p4
It seems to be caused by the audio tracks in Timeline.
JanNorden
Aug 23, 2017 08:47
Still getting this with player in Unity 2017.1.0f3.
Seneral
Aug 18, 2017 07:01
For me, it was caused by a corrupt particle system (thanks XEXYL), specifically one particle system that had the sub-emitter module enabled but not set up. Disabling it fixed the warnings:)
TooManySugar
Aug 09, 2017 15:04
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
2017.1f3
TooManySugar
Aug 09, 2017 15:03
I'm still getting this in 2017.1f3 anyone else?