Search Issue Tracker
Fixed
Fixed in 2022.3.26f1, 6000.0.0b14, 7000.0.0a1
Votes
2
Found in
2022.3.19f1
6000.0.0b11
7000.0.0a1
Issue ID
UUM-62793
Regression
No
Malloc(Temp) Pool keeps increasing when executing the Job.Run() in a thread
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/MemoryLeak/MemoryLeakTest.unity” Scene
3. Build and Run (File > Build Settings > Build and Run)
4. In Editor, open the Memory Profiler window (Window > Analysis > Memory Profiler)
5. Click on Player
6. In the Memory Profiler window, select Player as the target
7. Click “Capture”
8. Wait until the Scene is blue again
9. Repeat the step 5
10. In the Memory Profiler window, select Compare Snapshots
11. Select the 2 most recent Snapshots
12. Open the All Of Memory tab
13. Search for “malloc”
14. Expand Native, Unity Subsystem, UnsafeUtility
15. Observe the Size Difference of Malloc(Temp) Pool
16. Repeat steps 9-15
Expected result: Size Difference is the same
Actual result: Size Difference keeps increasing
Reproducible with: 1.0.0 (2023.0b5), 1.1.0 (2022.3.19f1, 2023.2.7f1, 2023.3.0b5)
Could not test with: 0.7.1-preview.1 (2021.3.34f1) (Could not find memory usage of Malloc)
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproduces in Play Mode and Windows Standalone Player
- Reproduces with Android Player
- Does not reproduce with Mono Scripting Backend
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
- The first frames are skipped when playing a video
- Text auto-scrolling can not work when naming assets/objects until backspace key is pressed
- Shadows are not cast when the Light's CullingMask and the GameObject's Layer do not match
- Graphics.DrawMeshInstanced does not work when 2D Renderer and 2D Shaders are used
- SpeedTree does not move when using WindZone
Resolution Note (fix version 7000.0.0a1):
This has been fixed.
Resolution Note (fix version 2022.3.26f1):
This was fixed in 2022.3.26f1.