Search Issue Tracker
Fixed
Fixed in 6000.3.10f1, 6000.4.0b10, 6000.5.0a8
Votes
0
Found in
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133429
Regression
No
Profiler Capture loading process is deferred until the final click is released when selecting a Capture in the Profiler list multiple times consecutively
Steps to reproduce:
- Create or open any Project
- Open the Profiler Window (Window > Analysis > Profiler)
- Set the Player Name to Edit Mode and Record Some Data
- Save the Capture via the Save button in the top right corner of the Window
- Click on the Capture in the Captures list to load it
- Click on the Capture multiple times in a row and observe the Profiler Window
Actual results: When selecting a Capture in the Profiler list multiple times consecutively, the loading process is deferred until the final click is released. Subsequently, the Capture will be loaded multiple times in succession, corresponding to the number of clicks. If Users double click the capture, it will load 2 times for no reason
Expected results: The Capture is loaded once and subsequent clicks aren't registered as actions to open the Capture until it is loaded once
Reproducible with versions: 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Can’t test with versions: 6000.0.67f1 (No Captures List feature)
Tested on (OS): Windows 11
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.5.0a8
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.4.0b10):
Fixed in 6000.4.0b10
Resolution Note (fix version 6000.3.10f1):
Fixed in 6000.3.10f1