Search Issue Tracker

Fixed in Unity 2017.3.0f3

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

  1. 4c88095137a945bcffce52c2d592714c?d=mm

    Saicopate

    Jun 19, 2018 17:20

    2018.1.5: error still here

  2. B4163e2bfc9148aca54e20d4bcfccc7b?d=mm

    jmitcheson

    May 28, 2018 05:15

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

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

  4. A1c98f76f3759b23702f67a3078b3032?d=mm

    solarisn

    Apr 30, 2018 01:52

    Having this issue in 2017.3.1p2

  5. D415da2476821df94df9a02fe7d23ce0?d=mm

    sirrus

    Apr 25, 2018 13:18

    Getting this error in 2017.4.1f1

  6. 6c839158f04f9f8046ceab192dbc2417?d=mm

    Dragmir

    Apr 02, 2018 10:44

    Not fixed in 2017.3.0f3

  7. E1944d6c266c507f6e4b512bda0cd14b?d=mm

    rstorm000

    Mar 18, 2018 18:48

    Is the fix of this coming to 5.6? Also people are still reporting it in general

  8. 62a43b0f3a37be834078aad1f3017c8a?d=mm

    Drathek

    Feb 20, 2018 11:45

    Also still getting this issue for me in Unity 2017.3.1f.

  9. Aac14c59fbf004df4adf8f8b99355d09?d=mm

    nadadi_91

    Feb 17, 2018 22:58

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

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

All about bugs

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