Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.2
2019.2.2f1
Issue ID
1180323
Regression
Yes
Memory leak in ShadowMapJobHeader
How to reproduce:
1. Build & Run the attached project for iOS
Actual result: "Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak" is getting spammed.
Reproducible with: 2019.2.0f1.
Not reproducible with: 2017.4.33f1, 2018.4.12f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a8.
Devices reproducible with:
- iPhone 6s (iOS 12.1.2)
Devices not reproducible with:
- iPhone 7 (iOS 12.1.2)
- iPhone X (iOS 13.0)
Notes:
- The errors doesn't appear in other versions, only 2019.2.
- “Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 5)” are spammed in 2019.2.10f1 (fixed)
-
eman8992
Apr 12, 2023 08:28
It happens with developing app. I have essaywriting.com.pk/term-paper-writing/ business for which I wanted to make an app, need some suggestion and guidance as well.
-
MichaelPerez123
Jun 15, 2022 19:54
sdasdadsaasd
-
shubhamswaraj2021
Aug 18, 2020 04:42
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
-
sergiocerone
May 27, 2020 02:01
The error has been fixed.
https://www.geometrydash.me/ -
Nolex
May 16, 2020 13:15
Problem still exists in 2019.2:
https://forum.unity.com/threads/jobtempalloc-has-allocations-that-are-more-than-4-frames-old.693394/
-
KevinStrootman
Jan 28, 2020 09:06
It is mostly happened in under developing apps and I had to face the exact same problems while launching an app for my academic writing service https://cheapessaywriter.com/assignment-writing-service and was succeeded in finding a way to resolve the respective issues but unfortunately later within few months it falls again to crumble and had to stop on that project
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.2):
The allocations are deleted in latest 2019.2 versions.