Search Issue Tracker

Fixed in 2017.3.0f3

Fixed in 5.6, 2017.1, 2017.2



Found in


Issue ID




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

Comments (86)

  1. E1944d6c266c507f6e4b512bda0cd14b?d=mm


    Jan 28, 2018 21:29

    got this again in 5.6.5p1

  2. 4fee16236885baca7a4ef33097b3144f?d=mm


    Jan 19, 2018 04:31

    It's not fixed in 2017.3.0f3...

  3. Eb1b364e99cbfbab5fadd32f3ac2c56b?d=mm


    Jan 18, 2018 13:58

    This is definitely not resolved and I can get just the editor into situations where it fairly quickly consumes all the memory in the system!

  4. 4d91a12973a190c05d42abe27c201f82?d=mm


    Jan 16, 2018 15:24

    It's not fixed, then...

  5. 6778fbeb93fd04fba3921c508cce40f1?d=mm


    Jan 11, 2018 16:03

    Oh, on 2017.3 it is the same.. damn

  6. 6778fbeb93fd04fba3921c508cce40f1?d=mm


    Jan 11, 2018 15:53

    Quite a troublemaker, can't do anything with that in Console. Needless to say that it produces massive Editor slow down.
    Unity Version: 2017.2.0f3 ( Never had any trees ).
    I know you fixed it in 2017.3 but can we ask for backport>?

  7. E1944d6c266c507f6e4b512bda0cd14b?d=mm


    Dec 17, 2017 07:13

    I think I've been able to stop this on one of my scenes by turning off light flares on all lights in the scene

  8. E1944d6c266c507f6e4b512bda0cd14b?d=mm


    Nov 27, 2017 00:26

    Still seeing this is 5.6.4p3

  9. 518202a1a2331309b877767f4e70cb7c?d=mm


    Nov 07, 2017 17:27

    I'm seeing the same problem today with 2017.2.0f3. Anyone found a fix yet?

  10. 104e7a27c612efac575ba55db7ae50cf?d=mm


    Oct 21, 2017 13:44

    I see it's apparently fixed in 2017.3. Will you be patching earlier versions of Unity to fix this?

    We're still getting it in 5.6.3p1.

All about bugs

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