Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1156652
Regression
No
Profile percentages for a CustomSampler change when recording is stopped. They are cleared when the profile is saved and loaded
How to reproduce:
1. Open the attached project "bug-profiler-load-timings.zip" and scene "SampleScene"
2. Open the Profiler window
3. Enter Play Mode
4. Search for and inspect the "Look at me!" sampler
5. Exit Play Mode
6. Inspect the "Look at me!" sampler's values again
7. Save the recorded profile to disk
8. Load the saved profile
9. Inspect the "Look at me!" timings again
Expected result: timing percentages for "Look at me!" don't change after exiting Play Mode and are identical after saving and loading the profile
Actual result: timings for "Look at me!" during recording are much larger than after exiting Play Mode. Also, the values for "Look at me" are cleared when the profile is saved and loaded from disk
Reproducible with: 2017.4.27f1, 2018.4.1f1, 2019.1.5f1, 2019.2.0b4, 2019.3.0a4
Notes: it appears that the "Self" value of the "Look at me!" sampler is added to its parent's "Self" value when the profile is loaded from disk
Comments (2)
-
KarlMogo
Nov 05, 2020 17:19
Look at me and my Percentage Calculator https://github.com/karllevi
-
KarlMogo
Nov 05, 2020 16:02
Actual result: gamedev.stackexchange.com
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
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a3