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

Scripting

-

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

  1. Response avatar

    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.

Comments (2)

  1. C1061425498cf311822c7928386a1d75?d=mm

    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

  2. Dd87acc155f95dce59ffbd5607395580?d=mm

    Tonyvaro1

    Feb 10, 2021 16:03

    This is very painful, very laggy

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.