Search Issue Tracker
Fixed
Fixed in 2020.3.42f1, 2021.3.14f1, 2022.2.0b15, 2023.1.0a23
Votes
0
Found in
2020.3.41f1
2021.2.10f1
2021.3.13f1
2022.2.0b13
2023.1.0a16
Issue ID
UUM-16733
Regression
No
JobTempAlloc has allocations that are more than 4 frames old' warnings are thrown when using AOVRequest and BatchRendererGroup
How to reproduce:
1. Open the user-submitted project
2. Open the scene "SampleScene" (Assets/Scenes/SampleScene.unity)
3. Enter Play mode and inspect the Console window (Window > General > Console)
Expected result: No warnings are seen
Actual result: 64 "Internal: JobTempAlloc" warnings are seen
Reproducible with: 12.1.4 (2021.2.10f1)
Could not test with: 7.7.1 (2019.4.35f1), 10.8.1 (2020.3.27f1)('AOVRequest' does not contain a definition for 'SetOverrideRenderFormat'), 13.1.5 (2022.1.0b6), 14.0.0 (2022.2.0a3)(There is no argument given that corresponds to the required formal parameter 'userContext' of 'BatchRendererGroup.BatchRendererGroup)
Full warning:
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note:
Closing internal bug ticket related to package code, as this issue has been fixed in the Unity Editor, instead of package side fixes.