Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4.29f1
2020.3.13f1
2020.3.21f1
2021.1.10f1
2021.2.0a18
Issue ID
1376488
Regression
Yes
Performance degrades when using GetComponents(List<T> results)
How to reproduce:
1. Open the user's attached project
2. Open scene Test
3. Press the Play button and observe the Console
Expected result: logged execution time of GetComponents is around 100ms
Actual result: logged execution time of GetComponents varies from around 500ms to over 1200ms
Reproducible with: 2019.4.29f1, 2019.4.32f1, 2020.3.13f1, 2020.3.22f1, 2021.1.10f1, 2021.1.23f1, 2021.2.0a18, 2022.1.0a1
Not reproducible with: 2019.4.28f1, 2020.1.0a1, 2020.3.12f1, 2021.1.0a1, 2021.1.9f1, 2021.1.24f1, 2021.1.28f1, 2021.2.0b14, 2021.2.1f1, 2022.1.0a10, 2022.1.0a14
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a6