Search Issue Tracker

Fixed in future release

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

  1. Cf0f9184e5cb55ed58b59a97cac59067?d=mm

    Twitch375

    Sep 07, 2017 04:37

    2017.1.0f3 Still getting this warning using up to date SteamVR.

  2. B75fdd7799e6849cfa974adb400e3f6a?d=mm

    Murray_Aurecon

    Sep 05, 2017 09:33

    Also seeing this issue in 2017.1.0f3. My scene is very simple. Using SteamVR. Frame rate is diabolical.

  3. 20dd0c6d1127a324db8bea2b1eca2467?d=mm

    ohbado

    Sep 03, 2017 09:25

    Still happens in 5.6.3p2.

  4. 7b05da8ca0232baf66a4a30dc0dd14b3?d=mm

    MikeHergaarden

    Aug 30, 2017 11:14

    FYI: 2017.1.0p5 claims to have fixed this, will take me a few days before I can confirm this.
    https://unity3d.com/unity/qa/patch-releases/2017.1.0p5

  5. 3662e998dbcb74e318fae9a367010da2?d=mm

    BoonDev

    Aug 30, 2017 03:10

    Still occurs in 5.6.3p1

  6. 77bf9c13d042dc017caca7db9bc93c89?d=mm

    Sir-Travisty

    Aug 29, 2017 22:27

    Still occurs in 2017.1.0f3 with Timeline and Audio tracks, if the audio asset is inactive when starting the editor.

  7. 2f1d46bd1d8390c9d1077265f29ae314?d=mm

    piger91

    Aug 29, 2017 10:01

    i get the issue while controling my Animations ,but it doesn't link to any script,what the hell is it? how can i fix it?

  8. 2630f7723ebe11cc1bb872e467fdd271?d=mm

    ionside

    Aug 26, 2017 06:00

    Still having this issue in 2017.1.0p4
    It seems to be caused by the audio tracks in Timeline.

  9. D50e5841c68f0ce40416caaf90a94000?d=mm

    JanNorden

    Aug 23, 2017 08:47

    Still getting this with player in Unity 2017.1.0f3.

  10. 427e41dd58434345696278acf9230a83?d=mm

    Seneral

    Aug 18, 2017 07:01

    For me, it was caused by a corrupt particle system (thanks XEXYL), specifically one particle system that had the sub-emitter module enabled but not set up. Disabling it fixed the warnings:)

All about bugs

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