Search Issue Tracker
By Design
Votes
13
Found in
2018.3.0f3
2018.4
2019.4
2020.2
2021.1
2021.2
Issue ID
1312038
Regression
No
Editor becomes unresponsive and performance is continually degraded when selecting a Scriptable Object with a large dataset
How to reproduce:
1. Open the attached project ("ScriptableObjectLargeDataset")
2. Select "Assets/data.asset"
Expected results: Inspector displays the view of the asset immediately and editor performance is unaffected
Actual result: Editor becomes unresponsive, the inspector then displays but editor performance is degraded
Reproducible with: 2018.4.32f1, 2019.4.20f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4
Comments (1)
-
Tonyvaro1
Feb 10, 2021 16:03
This is very painful, very laggy
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
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
Resolution Note:
It's by design that the Editor is unresponsive when a Scriptable Object has a very large string. String requires lots of extra-processing. A byte array is blittable and therefore much faster. The recommendation would be to use a different ScriptableObject for storage than the one for editing.