Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1231228
Regression
No
[Profile Analyzer] Marker Details revert to ordering by "Median" column when clicking "Analyze"
Reproduction steps:
1. Open attached project "ProfiAnalyze2020.2.zip"
2. In Profile Analyzer window, Load "capture1.pdata"
3. In "Marker details for currently selected range" window, click on the "Count Frame" column name
4. Click "Analyze"
Expected result: The "Marker details <...>" window remains sorted by "Count Frame"
Actual result: The "Marker details <...>" window reverts back to being sorted by "Median"
Reproducible with: 2018.4.20f1, 2019.3.8f1, 2020.1.0b4, 2020.2.0a5
Could not test with: 2017.4.38f1 (package version unavailable)
Reproducible with package versions: 0.4.0-preview.5, 0.6.0-preview.1
Could not test with package versions: 0.4.0-preview.3 (console errors)
Note:
Issue also reproduces when selecting a frame instead of clicking "Analyze"
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
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
Resolution Note (fix version 0.7.0-preview.1):
Now preserve columns sorting when Analyze is clicked