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
Comments (1)
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
yanivng
Dec 15, 2019 10:27
Any plans to backport the fix to 2018.4 LTS?