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

  1. 0f5409e3773c5bb88598ec09d7427576?d=mm

    Mushakushi

    Jul 26, 2018 00:40

    Edit: I am using unity 2D and I have NO terrain game objects in my scene, I've never even opened them in the entirety of my project.

  2. 0f5409e3773c5bb88598ec09d7427576?d=mm

    Mushakushi

    Jul 26, 2018 00:38

    This issue is still not fixed. Let me explain how it happened to me:
    I accidentally deleted my entire scripts folder (which contained all my scripts). There's a way to recover them, however. Via Recuva I restored an assetDatabase3 file. This opened up the version right before I deleted everything, after I clicked on it. It had been partially overriden by my Norton Security application on my Windows 10 computer. It only changed the size of my folders. And added some empty folders. I got the error: Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak. So it is not fixed :<

  3. F25db945e005add93f29ca8e53869f17?d=mm

    AmitSuri

    Jul 19, 2018 19:53

    Not fixed in 2018.2.0f2
    Note: I don't use any Terrain system.
    I get this in the Unity Editor.

    Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

    To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations

  4. 95d090d418ef37cc1449f083e8e97761?d=mm

    pigravity

    Jul 03, 2018 23:53

    Not fixed. 2018.2.0b4
    Seems it might make leaks for real, after some time unity crash hardly.

  5. 92b95da64bdc9ec33262a192e9837a04?d=mm

    drcrck

    Jul 03, 2018 12:41

    Not fixed.

  6. 18c6f0b3c142aa8be8e87e2e108b8392?d=mm

    stefan-velnita

    Jun 30, 2018 05:17

    Still not fixed - 2018.1.6f1

  7. 4c88095137a945bcffce52c2d592714c?d=mm

    Saicopate

    Jun 19, 2018 17:20

    2018.1.5: error still here

  8. B4163e2bfc9148aca54e20d4bcfccc7b?d=mm

    jmitcheson

    May 28, 2018 05:15

    Ugh - restarting Oculus "fixed" this. I guess there are many underlying root causes.

  9. B4163e2bfc9148aca54e20d4bcfccc7b?d=mm

    jmitcheson

    May 28, 2018 05:14

    Not fixed 2017.4.1f1.

    Happened after import of resources from another project, but not sure which ones exactly.

  10. A1c98f76f3759b23702f67a3078b3032?d=mm

    solarisn

    Apr 30, 2018 01:52

    Having this issue in 2017.3.1p2

All about bugs

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