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. D9d1665e889d7c301a1116ebde9ba137?d=mm

    kastus

    Jul 06, 2017 21:24

    5.6.2p2 - still happens

  2. D9d1665e889d7c301a1116ebde9ba137?d=mm

    kastus

    Jul 03, 2017 14:23

    Version 5.6.2p1 - problem still exists.

  3. 4351e8fc3dcf593b48740168f5e9e910?d=mm

    PendingFox

    Jun 26, 2017 12:28

    it hit's GPU so much. and also I have no trees or terrain whatsoever. version 5.6.1f1

  4. E0171497375b97cc0bf3693b004fea62?d=mm

    AntiSilence

    Jun 21, 2017 23:03

    I've also just noticed that I'm getting this issue, version 5.6.1f1

  5. D2e386df833ca1b97f243cc0c7f70ea7?d=mm

    Xexyl

    Jun 08, 2017 00:12

    I found a case where a particle system can become corrupted in a way that causes this warning to spew every frame. I submitted a bug with very simple project where the problem happens 100% of the time, so hopefully that will help. Will update with the tracking number when it shows up on issue tracker. (no trees involved in this case)

  6. E8cb935688bc1bd2390c754664fe879d?d=mm

    jhunter22

    Jun 07, 2017 12:36

    Note: this is not just in win32 builds, any windows build (win64 confirmed)

    I really don't get why Unity gives a 2017 beta prio over outstanding issues on the stable builds, they seem to greatly underestimate the impact of this bug.

  7. Fc629b042434bf71b9a4ae9e533d574d?d=mm

    GAMEDIA_Justin

    May 30, 2017 15:24

    This really hurts our performance and makes the output logs unreadable.

  8. 5576e30eb3b352b80cf4d1628ff2a286?d=mm

    kalineh

    May 24, 2017 01:27

    We have this bug in 5.6.1p1 with no trees in our scene.

  9. 2a2e240c722f11a980d9ab4b31f8bb31?d=mm

    frankadimcosta

    May 23, 2017 13:51

    Unity 5.6.1p1 has this bug.

  10. C6e450a3b8c08aa027fb7509ee4827da?d=mm

    Lymdun

    May 20, 2017 17:44

    Have the same problem.

All about bugs

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