Search Issue Tracker
Fixed
Fixed in 6000.3.9f1, 6000.4.0b8, 6000.5.X, 6000.5.0a7
Votes
2
Found in
6000.3.4f1
6000.4.0b3
6000.5.0a6
Issue ID
UUM-132332
Regression
Yes
100% crash rate when loading two profiler captures in the Profile Analyzer compare tool
Steps to reproduce:
- In Profiler, import profile capture 1
- Then import profile capture 2
- Click on profile capture 1 in profiler to load it
- In profile analyzer, click the compare option and load the current profile capture into the first slot
- Click on profile capture 2 in profiler to load it
- In profile analyzer, load the current profile capture into the second slot
- Wait for the white loading bar to complete
Actual results:
A complete Unity crash occurs 100% of the time
Expected results:
No crash occurs and profile analyzer works as normal
Reproducible with versions: Unity 6000.3.4f1, Unity 6000.4.0b3, Profile Analyzer 1.2.4
Tested on (OS): Windows 11 Enterprise
Notes:
- I recommend testing with the two attached profile captures
Refer to "Before_GemHunterMatch_2026-01-15_10-11-27.data" as "profile capture 1"
Refer to "After_GemHunterMatch_2026-01-15_10-26-10.data" as "profile capture 2"
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
Resolution Note:
Fixed in 6000.4.0b8
Resolution Note (fix version 6000.5.0a7):
A fix which greatly reduces memory usage has landed to stop the crash from happening. A second fix will land later to completely prevent the high memory situation from causing a crash.
Resolution Note (fix version 6000.5):
Fixed in 6000.4.0b8
Resolution Note (fix version 6000.4.0b8):
A fix which greatly reduces memory usage has landed to stop the crash from happening. A second fix has also landed to completely prevent the high memory situation from causing a crash.
Resolution Note (fix version 6000.3.9f1):
Fixed in 6000.3.9f1