Search Issue Tracker

Fixed in Unity 2017.3

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

-

-

Priority: 3Not yet prioritized for a release

-

Severity: 3Workaround is possible

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

  1. Aac14c59fbf004df4adf8f8b99355d09?d=mm

    nadadi_91

    Feb 17, 2018 22:58

    It's not fixed in Unity 2017.3.1f1...

  2. E2eaa96ca55899ba55c3c8f25ba80692?d=mm

    matt2405

    Feb 17, 2018 03:24

    Not fixed in 2017.3.0f3 - Error occurred with a timeline having a custom playable track and audio track.

  3. 0dde09ea729446570f99887508311e05?d=mm

    SaintTEmir

    Feb 14, 2018 01:21

    Unity 2013.3.1.1f same thing...

  4. 59f5dfe72e74cb7fe5e5540b803063bc?d=mm

    Soren11112

    Jan 31, 2018 21:40

    I am on 5.6.4f1 and the issue is certainly not resolved, seams related to .SetActive

  5. E1944d6c266c507f6e4b512bda0cd14b?d=mm

    rstorm000

    Jan 28, 2018 21:29

    again for me it seems to be caused by a combination of particles effects (maybe legacy ones?) + light flares turning on and off in the same view

  6. E1944d6c266c507f6e4b512bda0cd14b?d=mm

    rstorm000

    Jan 28, 2018 21:29

    got this again in 5.6.5p1

  7. 4fee16236885baca7a4ef33097b3144f?d=mm

    Parn-Manas

    Jan 19, 2018 04:31

    It's not fixed in 2017.3.0f3...

  8. Eb1b364e99cbfbab5fadd32f3ac2c56b?d=mm

    charleswcpalmer

    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!

  9. 4d91a12973a190c05d42abe27c201f82?d=mm

    elettrozero

    Jan 16, 2018 15:24

    It's not fixed, then...

  10. 6778fbeb93fd04fba3921c508cce40f1?d=mm

    TomekCoduar

    Jan 11, 2018 16:03

    Oh, on 2017.3 it is the same.. damn

All about bugs

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