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

Terrain

-

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

Comments (93)

  1. OpenfireGame

    May 31, 2019 04:06

    Not Fixed,
    2019.1.4,
    Directional Light "Mixed" Mode;
    Shadow Type : Soft Shadow;
    Light->Scene->Mixed Lighting: "Baked GI" check, Lighting Mode:Shadowmask;

  2. Tarrag

    Apr 20, 2019 17:01

    Also happens when building with AR Foundation and ARKit Unity 2018+ on built-in render pipeline and having shadows

  3. lee_unity808

    Mar 27, 2019 14:25

    2019.1.0b6 - issue is caused by enabling shadows on the directional light. Disabling shadows stops this error from logging out. Not acceptable.

  4. IEdge

    Mar 04, 2019 07:52

    Same here 2018.3.6f1

  5. Branxord

    Feb 12, 2019 17:45

    I have this when i bake my lightmaps and it's stuck at "5/11 Clustering | 1 jobs"

  6. Troas

    Jan 03, 2019 22:21

    Version 2018.3.0f2 this error occurred and resolved upon resetting unity. Have not been able to recreate it.

  7. oobartez

    Dec 12, 2018 14:46

    The issue is still unresolved in 2018.2.18f1 !!! We keep getting it all the time while using async navmesh.

  8. Keita-kun

    Dec 10, 2018 16:24

    I have version 2017.4.7.1f first time I have this issue:
    -Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak-
    My guess it just a slowdown in unity causing this issue since reloading same level playing it many times didn't reproduce the error. For me, warning showed up after level restart while testing only once.

  9. Flow-Hockey

    Dec 07, 2018 06:13

    Was there a consensus of what caused this? I'm getting this error in my project, and suddenly my prefabs don't have meshes. ugh.

  10. Flow-Hockey

    Dec 07, 2018 06:13

    Was there a consensus of what caused this? I'm getting this error in my project, and suddenly my prefabs don't have meshes. ugh.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.