Search Issue Tracker
Fixed in 2018.1.X
Votes
4
Found in
2017.1.1p1
Issue ID
953266
Regression
Yes
Having many elements in inspector, editor becomes extremely slow and an error is thrown
Steps to reproduce:
1. Download and open the attached project
2. Attach the ArcenAIMovementTypeData.cs script to a gameobject
3. Enter 70 or more in to the element count in any of the fields
4. Keep expanding them and observe preformance
Expected result: little to no performance impact
Actual result:
"Optimized GUI Block text buffer too large"
- 30+ editor starts slowing down
- 70+ editor becomes extremely unresponsive
- 150+ editor freezes entirely(set amount in 5.6, then imported back into 2017)
Reproduced on 2017.1.0a1, 2017.1.1p4, 2017.2.0f1, 2017.3.0b3
Not reproduced on 5.6.3p4*
Regression introduced in 2017.1.0a1
Notes: *5.6 appears to handle this much better, only having a significant performance impact impact past 150 parent elements
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
FiveFingerStudios
Jun 30, 2018 20:45
I'm currently experiencing this problem in 2017.4.3f1. I know this is fixed in Unity 2018.1.
But will this be fixed in the LTS 2017 branch? I don't want to upgrade to 2018.1 because I want to stay on a stable version of Unity.
David_Cheal
Feb 16, 2018 16:48
I've personally ran into this bug when using a custom [system.seralizable] class I had around 1000+ of these in a list, I don't know why you need to see them in inspector but my work around was simply something like this
if you have a list<GameObject> objects and its length is 1000 but you want to get the 25th object, create a public GameObject object and assign that to objects[25] then you can view that single one in the inspector.
MarinB
Jan 25, 2018 13:19
We have a list of around 1000 entries. Since the 2017 versions we are unable to view the list past 500 entries in the inspector . The editor starts to lag and sometimes even crashes. Items past the 500 mark aren't shown and we are unable to add extra entries.
PeterAtPayload
Nov 28, 2017 10:31
I have a long list - 5000+ entries. I can understand it's not reasonable to show all those entries in the editor, but the slow down (in unity 2017.2) means I can no longer inspect the offending asset. I can't even twirl the list closed as when it's selected as unity grinds to halt.