Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2018.2.0a1
2018.2.1f1
Issue ID
1086418
Regression
Yes
Rendering a scene with a Skinned Mesh Renderer without an Animator component causes a JobTempAlloc memory leak
How to reproduce:
1. Open the attached project
2. Enter Play Mode
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"
Reproducible with: 2018.2.0a1, 2018.2.16f1, 2018.3.0b11, 2019.1.0a9
Not reproducible with: 2017.4.15f1, 2018.1.9f2
Comments (1)
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
- Crash on vkGetInstanceProcAddr when setting graphics API to "Vulkan" on Fantasy Kingdom learning project
- Overlay Camera "clear depth" not working on Vulkan+Pixel8
- Shadows from Shadow Caster 2D using 2D Colliders show incorrectly when tiles are removed at runtime
- Stencil buffer is incorrectly cleared across Vulkan render passes during depth-only clear operations when using CommandBuffer API
- A non-existent webpage is opened when "Learn about Unity Build Automation" hyperlink is clicked
eric_funktroniclabs
Dec 18, 2018 17:54
Can we assume that we are not being effected by this bug if we are not seeing the `Internal` error being displayed?