Search Issue Tracker

Fixed in Unity 2017.3.0f3

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

-

-

Priority: 3Not yet prioritized for a release

-

Severity: 3Secondary functionality broken

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 (80)

  1. 9c544c4ce709ca4a1c642867c601c532?d=mm

    IEdge

    Mar 04, 2019 07:52

    Same here 2018.3.6f1

  2. 5722cce1c471d75be7b5d459b012a322?d=mm

    Branxord

    Feb 12, 2019 17:45

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

  3. 3f641f5d4e0b9d77a05af80ebd9471a8?d=mm

    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.

  4. 5be9032da92fb583e52738776694e31e?d=mm

    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.

  5. 18e25ee72b30d55723ff101c923e6dd6?d=mm

    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.

  6. 0cd730a5e8d3f8286f9b8df7500db9c9?d=mm

    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.

  7. 0cd730a5e8d3f8286f9b8df7500db9c9?d=mm

    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.

  8. 9a77a5947b745d8a53bf577cc42f02ce?d=mm

    ncortiz

    Oct 21, 2018 19:20

    Not fixed! Happens during reflection probe baking!

  9. Bbdccd6b3f71719a4fcc9e0f10361785?d=mm

    Rosehardt

    Oct 16, 2018 09:19

    Getting this issue in 2018.2.9f1

  10. C0f3c3a80cb2a83297f5c2d4fc2c9c9b?d=mm

    FlamingJohny

    Aug 12, 2018 16:44

    not fixed 2018.2.2f1

All about bugs

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