Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.3
2018.3.3f1
2019.1
2019.2.0a1
Issue ID
1142394
Regression
No
Capturing a memory snapshot takes forever when memory heap is large
Reproduction steps:
1. Open the attached project inside of "1142394.zip"
2. Open and play "SampleScene"
3. Open the Memory Profiler inside Window -> Analysis -> Memory Profiler
4. Inside the Memory Profiler, click on "Capture Player"
Expected result: The Memory capture completes eventually
Actual result: The Memory capture never completes and hangs Unity Editor
Reproduces on: 2018.3.12f1, 2019.1.0b10, 2019.2.0a10, Package version 0.1.0-preview.6
Could not reproduce on pre-2018.3.0f1 due to missing namespaces for the package and 2019.1 early versions crash due to GC crash
Note:
- Test project requires over 8 Gigabytes of unallocated RAM
- No Input/Output activity can be seen with the system's local disks
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
yanivng
Dec 15, 2019 10:27
Any plans to backport the fix to 2018.4 LTS?