Search Issue Tracker

Fixed in 2017.3.0f3

Fixed in 5.6.X, 2017.1.X, 2017.2.X



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

  1. Eb2be104bb042b0bd83d309c4bb3b7c6?d=mm


    Aug 11, 2020 10:24!/;area=summary;u=341770;u=4039!/;area=summary;u=341718!/!/!/!/

  2. 41e194bc6932baeaeb2e633c28d0830a?d=mm


    Jul 28, 2020 10:13;u=245304;u=19154;u=556429;;u=245305;;u=19155;u=556432;;u=556433;u=245302;;u=556434,,,,

  3. Ac206eb0677a3efbb97218dbc79f9eff?d=mm


    Feb 07, 2020 10:57

    Hey everyone, if shadows is causing this error message again, make a new bug report with that in the title, this one is only regarding the terrain trees. I doubt anyone from Unity is still checking the comments here seeing as it's marked as fixed already. With a new bug report, they will be taking a look at it.

  4. Ab7a038ec81f7fe41fa9cd5ffdb97091?d=mm


    Jan 27, 2020 20:02

    Unity 2017.4.31

    Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
    0x000007FEDBB5CF2C (UnityPlayer) StackWalker::GetCurrentCallstack
    0x000007FEDBB610EF (UnityPlayer) StackWalker::ShowCallstack
    0x000007FEDB73C1ED (UnityPlayer) GetStacktrace
    0x000007FEDB5A5B80 (UnityPlayer) DebugStringToFile
    0x000007FEDB5A5EB1 (UnityPlayer) DebugStringToFile
    0x000007FEDB3D75A3 (UnityPlayer) ThreadsafeLinearAllocator::FrameMaintenance
    0x000007FEDB3D48C0 (UnityPlayer) MemoryManager::FrameMaintenance
    0x000007FEDB5D7E8F (UnityPlayer) PlayerLoop
    0x000007FEDBB79764 (UnityPlayer) PerformMainLoop
    0x000007FEDBB78B3A (UnityPlayer) MainMessageLoop
    0x000007FEDBB7B0EC (UnityPlayer) UnityMainImpl
    0x000007FEDBB7B2DB (UnityPlayer) UnityMain
    0x000000013FBC13EE (AgentRoswell) __scrt_common_main_seh
    0x00000000772A652D (kernel32) BaseThreadInitThunk
    0x00000000774DC521 (ntdll) RtlUserThreadStart

  5. Dd28d9e33654c2151715cef9e0f269aa?d=mm


    Jan 14, 2020 16:26

    On 2019.1.14 - same as LEE_UNITY808. Issue is caused if shadows enabled on the directional light. Disabling it stop this error.

  6. 082e0add4fc86ad6e5e8c5b6d7a923dd?d=mm


    Nov 15, 2019 13:56

    Still not fixed in 2019.1.5f1 with shadows enabled.

  7. 78904e4c0f2c31837b41938072655785?d=mm


    Sep 23, 2019 22:48

    the solution: go to directional light _ shadow type_ turn on to no shadow

  8. F8946453d84732986fcef0b7465ed990?d=mm


    Jul 03, 2019 23:57

    For this is happening when I play Timelines (Playable Director) and seems to hurt the performance.

  9. Ab9748b09a7d7666efa50b9eac1ca47c?d=mm


    Jun 24, 2019 20:16

    Is there a new open ticket for this issue? I can't vote on this issue because it's marked as closed.

  10. 4c88095137a945bcffce52c2d592714c?d=mm


    Jun 10, 2019 09:44

    Not fixed in Unity 2019.1.5 + AR Foundation 2.1, soft Shadows enabled.

Add comment

Log in to post comment

All about bugs

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