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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
sameer-mirza
Jul 31, 2017 10:59
I'm getting this when I try to minimize a build using native Windows functions. In minimized state I keep getting this until I restore the window or close it (version 5.6.2f1)
sinvent
Jul 27, 2017 14:07
Still happens in 2017.1p1, please fix it!
MikeHergaarden
Jul 27, 2017 12:42
Still happens in 2017.1p1
Diggidy
Jul 26, 2017 22:18
What version is this fixed in? Currently using 5.6.2p3 and still getting this error.
Gregorik
Jul 24, 2017 21:51
Getting it in 5.6.2f1 editor, and it's a bad one.
LunarExGames
Jul 19, 2017 22:45
Getting the error "Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak" then it'll eventually crash the program. Can't release the game this way!
philc_uk
Jul 11, 2017 22:15
Seriously - Unity!!! Please fix this ASAP / Release to the older versions..!!
MikeHergaarden
Jul 11, 2017 08:35
So this is now marked as "fixed in the future"...What version though?
mushdevstudio
Jul 10, 2017 05:27
5.6.2p2 - still happening and is really killing performance.
kastus
Jul 06, 2017 21:24
5.6.2p2 - still happens