Search Issue Tracker

Fixed in Unity 2017.3.0f3



Found in


Issue ID




JobTempAlloc error appears in Standalone Build output log if trees are in the Scene




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

  1. Eb49d39c2fe6fba89d1157093ee38838?d=mm


    Jul 31, 2017 10:59

    I'm getting this when I try to minimize a build using native Windows functions. In minimized state I keep getting this until I restore the window or close it (version 5.6.2f1)

  2. 4221e72b84e651dac90d10372316dc1b?d=mm


    Jul 27, 2017 14:07

    Still happens in 2017.1p1, please fix it!

  3. 7b05da8ca0232baf66a4a30dc0dd14b3?d=mm


    Jul 27, 2017 12:42

    Still happens in 2017.1p1

  4. Aa84590a4249a54b5af2413a25bb30a7?d=mm


    Jul 26, 2017 22:18

    What version is this fixed in? Currently using 5.6.2p3 and still getting this error.

  5. 7935161fb26c5f49b347104ef1f4a026?d=mm


    Jul 24, 2017 21:51

    Getting it in 5.6.2f1 editor, and it's a bad one.

  6. Aa109ca31675c6ff4d75647c065add95?d=mm


    Jul 19, 2017 22:45

    Getting the error "Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak" then it'll eventually crash the program. Can't release the game this way!

  7. Ab7a038ec81f7fe41fa9cd5ffdb97091?d=mm


    Jul 11, 2017 22:15

    Seriously - Unity!!! Please fix this ASAP / Release to the older versions..!!

  8. 7b05da8ca0232baf66a4a30dc0dd14b3?d=mm


    Jul 11, 2017 08:35

    So this is now marked as "fixed in the future"...What version though?

  9. D0ebd839dcb75b2e883a79f42dd6732d?d=mm


    Jul 10, 2017 05:27

    5.6.2p2 - still happening and is really killing performance.

  10. D9d1665e889d7c301a1116ebde9ba137?d=mm


    Jul 06, 2017 21:24

    5.6.2p2 - still happens

All about bugs

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