Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b12
2018.1.4f1
2018.2.0a4
Issue ID
1049489
Regression
Yes
In Profiler, most of the "CPU Usage" details are missing when the saved profile data is loaded
How to reproduce:
1. Open attached project "NavMeshTest.zip" and scene "NavMeshTest"
2. Open Profiler window and enable "Record"
3. Enter Play mode
4. In Profiler window, press Save and save the profile data
5. Exit Play mode
6. In Profiler window, press Clear and then Load saved profile data
7. In Profiler window, highlight CPU Usage and observe Profiler Hierarchy
Expected result: all the data is shown when saved and loaded in Profiler
Actual result: most of the data is not shown in Profiler after loading the data
Reproducible with: 2018.1.0b12, 2018.1.5f1, 2018.2.0a4, 2018.2.0b7, 2018.3.0a2
Not reproducible with: 2017.4.6f1, 2018.1.0b11, 2018.2.0a3
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
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
This is a duplicate of issue #1047081