Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
1
Found in
2021.3.42f1
2022.3.42f1
6000.0.15f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-82199
Regression
No
A Memory leak occurs when the "JsonSerialization.FromJson" function is executed
How to reproduce:
1. Open the “JsonMemoryBug.zip“ project
2. Open the “Assets/TryFromJson/SerializationBugExample1.unity” Scene
3. Enter Play Mode
4. Observe the Console
Expected result: Nothing is logged
Actual result: A Memory leak warning is logged
Reproducible in: 2021.3.42f1, 2022.3.42f1, 6000.0.15f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- Full warning reads: “Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak”
- The Serialization package (com.unity.serialization) is required for the reproduction
- Reproducible both with "JsonSerialization.FromJson" and "JsonSerialization.TryFromJson" functions
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
- RenderTexture content from 'Depth Only' camera is not rendered correctly on UI RawImage when Multithreaded Rendering is enabled on specific MediaTek devices.
- Weight Brush Overlay text is clipped in Sprite Editor
- GameObject Transform scale values reset to their previously saved values when proportions are constrained and certain decimal values are entered in the Inspector
- Asset thumbnails in the Project window stay white when a referenced texture file is deleted and restored
- Crash on PersistentManager::ReadObjectThreaded when calling AssetDatabase.ForceReserializeAssets() multiple times in a row
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.