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
-
ezrahidaya
Nov 04, 2023 09:53
Oh, I've encountered this issue before, and it's quite frustrating! It's disappointing when you're working on a project uaeassignmenthelp.ae/ and the editor becomes unresponsive like this. I appreciate it helps to know if there have been any improvements or not.
-
wasaelmarketing
Feb 20, 2022 10:46
I can't find the location which you've mentioned above "Assets/XFrame/TestScene/Scene" also I'm not getting the same result for HTTPS://wasaelgroup.com/ my effort is to keep going to waste please sort this 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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.