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: 3Secondary functionality broken

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

  1. 6778fbeb93fd04fba3921c508cce40f1?d=mm

    TomekCoduar

    Jan 11, 2018 16:03

    Oh, on 2017.3 it is the same.. damn

  2. 6778fbeb93fd04fba3921c508cce40f1?d=mm

    TomekCoduar

    Jan 11, 2018 15:53

    Quite a troublemaker, can't do anything with that in Console. Needless to say that it produces massive Editor slow down.
    Unity Version: 2017.2.0f3 ( Never had any trees ).
    I know you fixed it in 2017.3 but can we ask for backport>?

  3. E1944d6c266c507f6e4b512bda0cd14b?d=mm

    rstorm000

    Dec 17, 2017 07:13

    I think I've been able to stop this on one of my scenes by turning off light flares on all lights in the scene

  4. E1944d6c266c507f6e4b512bda0cd14b?d=mm

    rstorm000

    Nov 27, 2017 00:26

    Still seeing this is 5.6.4p3

  5. 518202a1a2331309b877767f4e70cb7c?d=mm

    kdragos

    Nov 07, 2017 17:27

    I'm seeing the same problem today with 2017.2.0f3. Anyone found a fix yet?

  6. 104e7a27c612efac575ba55db7ae50cf?d=mm

    daisySa

    Oct 21, 2017 13:44

    I see it's apparently fixed in 2017.3. Will you be patching earlier versions of Unity to fix this?

    We're still getting it in 5.6.3p1.

  7. 2a2e240c722f11a980d9ab4b31f8bb31?d=mm

    frankadimcosta

    Oct 19, 2017 20:14

    Still here in 2017.2.0f3.

  8. Cf0f9184e5cb55ed58b59a97cac59067?d=mm

    Twitch375

    Sep 07, 2017 04:37

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

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

  10. 20dd0c6d1127a324db8bea2b1eca2467?d=mm

    ohbado

    Sep 03, 2017 09:25

    Still happens in 5.6.3p2.

All about bugs

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