Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1233077
Regression
No
Frame values do not fit in the Profile Analyzer Summary fields when they have 6 or more digits
How to reproduce:
1. Create a new project
2. Import the Profile Analyzer package from the Package Manager
3. Open the Profile Analyzer window (Window -> Analysis -> Profile Analyzer)
4. Open the Profiler window (Window -> Analysis -> Profiler)
5. Enter the Play Mode
6. Pull the Data into Profile Analyzer after the Profiler records more than 99999 frames (6 or more digits)
Expected result: all frame values fit into Profile Analyzer Summary fields
Actual result: 6 or more digit frame values do not fit into Profile Analyzer Summary fields
Reproducible with: 0.4.0 - preview.5 (2018.4.20f1), 0.4.0 - preview.6 (2019.3.7f1), 0.5.0 - preview.1 (2020.1.0b3), 0.6.0 - preview.1 (2020.2.0a5)
Could not test with package versions: 0.4.0 - preview.3 (could not load the data)
Notes:
This issue does not occur when loading already saved .pdata files
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
- Crash on TextCore::OTL_TableReader::GetOpenTypeLayoutTables when using Japanese Font as TMP Fallback
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
Resolution Note (fix version 1.0.0):
Large Frame Values not fit inside the box