Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.4.0-preview.6
Issue ID
1232226
Regression
Yes
[Profile Analyzer] Compare - Loading data over the top of existing data gives unclear warnings when a frame range is selected
Reproduction steps:
1. Open attached project "ProfiAnalyze2020.2.zip"
2. In Profile Analyzer window, go to the Compare tab then load "cap1.pdata" and "cap2.pdata"
3. Make sure "Pair Graph Selection" is checked
4. Select frames 273 to 286
7. Load "smallcapture.pdata" into the 2nd data slot
8. Check Console window for warnings
Expected result: No warnings are printed
Actual result: "Frame <...> exceeds range" warnings are printed
Reproducible with: 2018.4.20f1, 2019.3.8f1, 2020.1.0b4, 2020.2.0a5
Could not test with: 2017.4.39f1 (package version unavailable)
Reproducible with package versions: 0.5.0-preview.1, 0.6.0-preview.1
Not reproducible with package versions: 0.4.0-preview.5, 0.4.0-preview.6
Could not test with package versions: 0.4.0-preview.3 (console errors)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 0.7.0-preview.1):
Fixed console warning when loading data over the top of existing data