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
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
drcrck
Jul 03, 2018 12:41
Not fixed.
stefan-velnita
Jun 30, 2018 05:17
Still not fixed - 2018.1.6f1
Saicopate
Jun 19, 2018 17:20
2018.1.5: error still here
jmitcheson
May 28, 2018 05:15
Ugh - restarting Oculus "fixed" this. I guess there are many underlying root causes.
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.
solarisn
Apr 30, 2018 01:52
Having this issue in 2017.3.1p2
sirrus
Apr 25, 2018 13:18
Getting this error in 2017.4.1f1
Dragmir
Apr 02, 2018 10:44
Not fixed in 2017.3.0f3
rstorm000
Mar 18, 2018 18:48
Is the fix of this coming to 5.6? Also people are still reporting it in general
robbob44
Feb 20, 2018 11:45
Also still getting this issue for me in Unity 2017.3.1f.