Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1229973
Regression
No
[Profile Analyzer] 1 frame referred to as "1 frames" in Frame Summary tooltip
Reproduction steps:
1. Open attached project "ProfileAnalyze.zip"
2. In Profile Analyzer window, Load "case_1229216-capture.pdata"
3. In Frame Summary window, hover over the 10th line
Expected result: Tooltip says "1 frame"
Actual result: Tooltip says "1 frames"
Reproducible with: 2018.4.19f1, 2019.3.7f1, 2020.1.0b3, 2020.2.0a4
Could not test with: 2017.4.38f1 (package version unavailable)
Reproducible with package versions: 0.4.0-preview.3, 0.6.0-preview.1
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 (fix version 0.7.0-preview.1):
1 frame no longer referred to as "1 frames"