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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 0.7.0-preview.1):
Optimisations applied to the top N marker area and the thread summary list