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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Add comment