Search Issue Tracker

Fixed in 2017.3.0f3

Fixed in 5.6, 2017.1, 2017.2

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

  1. 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.

  2. 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.

  3. 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.

  4. 9a77a5947b745d8a53bf577cc42f02ce?d=mm

    ncortiz

    Oct 21, 2018 19:20

    Not fixed! Happens during reflection probe baking!

  5. Bbdccd6b3f71719a4fcc9e0f10361785?d=mm

    Rosehardt

    Oct 16, 2018 09:19

    Getting this issue in 2018.2.9f1

  6. C0f3c3a80cb2a83297f5c2d4fc2c9c9b?d=mm

    FlamingJohny

    Aug 12, 2018 16:44

    not fixed 2018.2.2f1

  7. 12f8b1d899b95dbcab59e7eade28a119?d=mm

    GrandBOOM

    Aug 07, 2018 15:49

    Not fixed 2018.2.0f2

  8. 43029fd903666cef9cd7cc24aa05263c?d=mm

    Alardaen

    Aug 04, 2018 15:05

    Still having the issue when switching SkinnedMeshes on unity 2018.2.0f2, it seems related to materials (shaders) in my case, under 2017.4.6 everything is fine, so, yeah downgrading the project to keep working normally

  9. 76d5dfe5406ffa477333b8674eb29c10?d=mm

    mick129

    Aug 03, 2018 16:19

    Not fixed for me..

  10. 31f1ca784f185ae42297814768e697e7?d=mm

    dontdiedevelop

    Aug 03, 2018 11:31

    this issue not fixed i'm still having same error
    2018.2.1f1

All about bugs

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