Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2019.4.5f1
2021.1
Issue ID
1283344
Regression
No
[Profiler] The CPU Frame chart doesn't scale with the data when the data is loaded in
How to reproduce:
1. Create a new project
2. Open the Profiler (Window->Analysis->Profiler)
3. Make sure that the CPU Module is enabled (drop-down Module list in the top left of the Profiler window and check the CPU Module)
4. Load in the attached "Data01.data" into the Profiler (load from a file button at the top right of the Profiler window)
Expected results: The CPU Frame charts scale with the loaded in data
Actual results: The CPU Frame charts do not scale with the loaded in data
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a2
Notes:
- Pressing on the elements in the Module details panel (Hierarchy, Timeline, and Raw Hierarchy all give the same effect) will fix the CPU Frame chart to show as it supposed to, after every press the Frame chart will move a bit closer to the correct size
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
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (fix version 2021.1):
Fixed issue with wrong chart scale after profiler capture load
Fixed in 2021.1.0a9