Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0a3
2018.3.12f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1147549
Regression
Yes
First time entering playmode extremely slow when project contains many ScriptableObject assets
Steps to repro:
1. Open attached project
2. Enter Play Mode
Expected result: Editor takes 1-2 seconds to enter Play Mode (like in 2018.2)
Actual result: Editor takes 110+ seconds to enter Play Mode
Reproduced in: 2018.4.0f1, 2019.1.2f1, 2019.2.0b1, 2019.3.0a2
Not reproduced in: 2018.3.0a2
Note:
1. Entering Play Mode second time is way faster.
2. The project contains several thousand Tilemap tile assets, removing these from the project drops the first time Play Mode startup time significantly.
3. Profiler shows "enterPlayModePreWaeake.Invoke takes 114904ms, on the second play it takes only around 4.
-
Resolution Note (2019.3.X):
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
This is a duplicate of issue #1136349