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
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
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
- Crash on mdb_node_search when opening a project
- [macOS] Unable to install VisionOS Module on Hub
- NullReferenceException is thrown when pressing the "Enter" key to select an item in a ListView
- Burst internal compiler errors are thrown when creating a new 2D project
DrunkenMastah
Jul 19, 2018 19:53
Not fixed in 2018.2.0f2
Note: I don't use any Terrain system.
I get this in the Unity Editor.
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
To Debug, enable the define: TLA_DEBUG_STACK_LEAK in ThreadsafeLinearAllocator.cpp. This will output the callstacks of the leaked allocations
pigravity
Jul 03, 2018 23:53
Not fixed. 2018.2.0b4
Seems it might make leaks for real, after some time unity crash hardly.
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