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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
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
TomekCoduar
Jan 11, 2018 15:53
Quite a troublemaker, can't do anything with that in Console. Needless to say that it produces massive Editor slow down.
Unity Version: 2017.2.0f3 ( Never had any trees ).
I know you fixed it in 2017.3 but can we ask for backport>?
rstorm000
Dec 17, 2017 07:13
I think I've been able to stop this on one of my scenes by turning off light flares on all lights in the scene
rstorm000
Nov 27, 2017 00:26
Still seeing this is 5.6.4p3
kdragos
Nov 07, 2017 17:27
I'm seeing the same problem today with 2017.2.0f3. Anyone found a fix yet?
daisySa
Oct 21, 2017 13:44
I see it's apparently fixed in 2017.3. Will you be patching earlier versions of Unity to fix this?
We're still getting it in 5.6.3p1.
frankadimcosta
Oct 19, 2017 20:14
Still here in 2017.2.0f3.
Twitch375
Sep 07, 2017 04:37
2017.1.0f3 Still getting this warning using up to date SteamVR.
Murray_Aurecon
Sep 05, 2017 09:33
Also seeing this issue in 2017.1.0f3. My scene is very simple. Using SteamVR. Frame rate is diabolical.