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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment