Search Issue Tracker
Fixed in 2019.1.X
Duplicate in 2019.4.X
Votes
0
Found in
2018.4
2018.4.19f1
2019.1
Issue ID
1242943
Regression
No
ManagedHeap UsedSize leaking memory when MemorySnapshot RequestNewSnapshot in package is called and Allow Unsafe Code is enabled
How to reproduce:
1. Open attached project "MemorySnapshotLeakSampleZip.zip"
2. Open the Package Manager and add a local package from disk; the package is located in the project's root directory(MemorySnapshotLeakPackage).
3. Open the Profiler window and start profiling the Editor while looking at the Memory module(Used total and Mono)
4. From the Menu Bar select Memory Snapshot Test and click the only button in the window that pops up to take memory snapshot
5. Note the memory usage after a snapshot is taken. Each time the snapshot is taken, the Mono memory increases exponentially and does not get cleared.
Expected result: the memory usage stops increasing at around 100-200Mb
Actual result: Mono memory increases exponentially and does not get cleared
Reproducible with: 2018.4.23f1, 2019.1.0a5
Fixed in: 2019.1.0a6 and above
Notes:
The issue is only reproducible on Windows, could not reproduce on macOS
The issue is only reproducible when the package contents are imported as a package
The issue is only reproducible when 'Allow unsafe code' in the package .asmdef is enabled
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2019.1):
Verified in:
2019.1.0a6