Search Issue Tracker
Fixed in 1.1.0-preview.2
Votes
0
Found in [Package]
1.0.3
Issue ID
1281270
Regression
No
[Profile Analyzer] Marker Summary Max and Individual Max values have links to Frame 0
How to reproduce:
1. Open the attached "case_1281270.zip" project
2. Open Profiler
3. Capture some data
4. Open Profiler Analyzer
5. Select Pull Data option
6. In the Marker Details window, select Texture Memory
7. In the Marker Summary section, click the Max link to Frame 0
8. Observe the warning in the Console window
Expected result: Max value does not have a link to Frame 0
Actual result: Warning that Frame 0 does not exist occurs in the Console window
Reproducible with: 0.4.0-preview.6 - 1.0.3(2018.4.27f1, 2019.4.12f1, 2020.1.8f1, 2020.2.0b5)
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
Add comment