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
-
codyraslin
May 20, 2021 13:28
This always happen to me. I learned that updating the system will resolve this issue. Why does the system doesn't have an auto-update? Anyway, if you want help with your assignments and term paper writing, I recommend a-writter.com. They have the best and experienced writers, I know because I already purchased their service for myself. Check them out
-
gingersdas34
Apr 16, 2021 07:22
The same things happened to me when I was working for camscanner apk TechBigs
-
oliviaark765
Apr 12, 2021 11:53
The same things happened to me when I was working for cryptoexchangesoftware.net/ and Did the same thing as you mentioned above It is the best possible solution for improving the response and performance
-
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
- OnApplicationPause pauseStatus is incorrect after losing focus on macOS
- Animator Blend Tree weight defaults to 0 for a frame when AnimationClipPlayable is created with script in Play Mode
- Memory gets allocated for GC each frame when using PrefabStageUtility.GetPrefabStage
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- [Preset] Some properties cannot be excluded from Texture Importer Preset through the Inspector window
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.