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
- “Assemblies” and “Areas” tabs disappears after switching to Scene tab and back in the Assemblies filter window
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
Resolution Note (fix version 0.7.0-preview.1):
Now preserve columns sorting when Analyze is clicked