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

  2. Ab7a038ec81f7fe41fa9cd5ffdb97091?d=mm


    Jul 11, 2017 22:15

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

  3. 7b05da8ca0232baf66a4a30dc0dd14b3?d=mm


    Jul 11, 2017 08:35

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

  4. D0ebd839dcb75b2e883a79f42dd6732d?d=mm


    Jul 10, 2017 05:27

    5.6.2p2 - still happening and is really killing performance.

  5. D9d1665e889d7c301a1116ebde9ba137?d=mm


    Jul 06, 2017 21:24

    5.6.2p2 - still happens

  6. D9d1665e889d7c301a1116ebde9ba137?d=mm


    Jul 03, 2017 14:23

    Version 5.6.2p1 - problem still exists.

  7. 4351e8fc3dcf593b48740168f5e9e910?d=mm


    Jun 26, 2017 12:28

    it hit's GPU so much. and also I have no trees or terrain whatsoever. version 5.6.1f1

  8. E0171497375b97cc0bf3693b004fea62?d=mm


    Jun 21, 2017 23:03

    I've also just noticed that I'm getting this issue, version 5.6.1f1

  9. D2e386df833ca1b97f243cc0c7f70ea7?d=mm


    Jun 08, 2017 00:12

    I found a case where a particle system can become corrupted in a way that causes this warning to spew every frame. I submitted a bug with very simple project where the problem happens 100% of the time, so hopefully that will help. Will update with the tracking number when it shows up on issue tracker. (no trees involved in this case)

  10. E8cb935688bc1bd2390c754664fe879d?d=mm


    Jun 07, 2017 12:36

    Note: this is not just in win32 builds, any windows build (win64 confirmed)

    I really don't get why Unity gives a 2017 beta prio over outstanding issues on the stable builds, they seem to greatly underestimate the impact of this bug.

All about bugs

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