Search Issue Tracker
Fixed
Fixed in 1.1.3
Votes
3
Found in [Package]
1.1.0
Issue ID
PROFB-191
Regression
Yes
“Opening snapshot” window stuck on "Crawling GC handles" process when opening a Snapshot
How to reproduce:
1. Open the “Blank22-3-8“ project
2. Open the Memory Profiler (Window > Analysis > Memory Profiler)
3. Select the “MacOS Without Coroutine” Snapshot
Expected result: The snapshot is opened
Actual result: The “Opening snapshot” window is constantly stuck on the “Crawling GC handles” process
Reproduced with: 1.1.0-pre.3 ( 2022.3.12f1), 1.1.0 (2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a14)
Not reproducible with: 0.7.1-preview.1 (2021.3.32f1), 1.1.0-pre.1 ( 2022.3.12f1)
Reproduced on: Windows 11, macOS 12.6.1
Not reproducible on: No other environment tested
Note: Not reproducible when creating a snapshot in affected streams and opening it
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
MikeLymanTurbine
Oct 30, 2024 20:17
Would love to get this fixed, it's preventing us from reliably using the memory profiler