Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
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
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 (93)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Baked Lightmap ”View” button text is aligned incorrectly
- Lightmap Asset icon changes colours after Baked Lightmap Viewer window is opened
- VideoClipImporter preset not applied when applying Preset Selector on already imported video clips
- Frame Debugger gets disabled when any Editor window is maximised and minimised
- TextMeshPro InputField view is not updated when OnEndEdit is triggered
nadadi_91
Feb 17, 2018 22:58
It's not fixed in Unity 2017.3.1f1...
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.
SaintTEmir
Feb 14, 2018 01:21
Unity 2013.3.1.1f same thing...
Soren11112
Jan 31, 2018 21:40
I am on 5.6.4f1 and the issue is certainly not resolved, seams related to .SetActive
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
rstorm000
Jan 28, 2018 21:29
got this again in 5.6.5p1
Parn-Manas
Jan 19, 2018 04:31
It's not fixed in 2017.3.0f3...
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!
elettrozero
Jan 16, 2018 15:24
It's not fixed, then...
TomekCoduar
Jan 11, 2018 16:03
Oh, on 2017.3 it is the same.. damn