Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1235707
Regression
No
A performance decrease occurs when excluding multiple Profile Analyzer Markers from the Marker list
How to reproduce:
1. Create a new project
2. Import the Profile Analyzer package from the Package Manager
3. Open the Profile Analyzer window (Window -> Analysis -> Profile Analyzer)
4. In the Profile Analyzer window click the Single tab and load the attached pdata file
5. Make sure that 'Exclude names' is set to 'Any'
6. In the Marker list select any Marker and choose "Add to Exclude Filter"
7. Repeat the 6th step multiple times (a few is enough for the delay to become obvious but the more it's done the longer the delays gets)
Expected result: the selected Marker gets removed from the Marker List
Actual result: the selected Marker gets removed from the Marker List and the Profile Analyzer window delay increases
Reproducible with: 0.4.0 - preview.3 (2018.4.21f1), 0.4.0 - preview.5 (2018.4.21f1), 0.4.0 - preview.6 (2018.4.21f1), 0.5.0 - preview.1 (2019.3.10f1), 0.6.0 - preview.1 (2020.1.0b5, 2020.2.0a7)
Notes:
Identical behaviour when working in the Compare tab
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 0.7.0-preview.1):
Optimisations applied to the top N marker area and the thread summary list