Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
0
Found in
2020.2.0a13
2021.1
2021.1.0a10
Issue ID
1297993
Regression
Yes
ReorderableList allocates a lot of memory when inspecting multiple targets
How to reproduce:
1. Open the attached project
2. In the Hierarchy search for "test" and select all of the objects
3. In the object Inspector interact with the array script (fold unfold array fields, add components, etc)
4. Observe the poor performance
Expected result: the Inspector is fully functional and performant even when multi selecting objects
Actual result: the Inspector is slow when multi selecting objects with reorderablelist arrays
Reproducible in:2021.1.0a9, 2020.2.0f1, 2020.2.0a13
Not reproducible in: 2020.2.0a12, 2020.1.17f1, 2019.4.16f1, 2018.4.30f1, 2017.4.40f1 (these versions do not use the reorderable list control by default and thus don't suffer the performance downgrade)
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
Add comment