Search Issue Tracker
Fixed
Under Consideration for 1.0.X
Votes
7
Found in [Package]
1.0.4
Issue ID
SEQ-1396
Regression
No
SequenceAssetIndexer.InitializeWithExistingData adds overhead when entering Play Mode in a heavy project
Reproduction Steps:
# Open the attached project
# Enter Play Mode
# Observe delayCall callbacks locking up for a few seconds right after the initial application reload
Expected result: there is no significant overhead from Sequences-related code when entering the play mode
Actual result: SequenceAssetIndexer.InitializeWithExistingData subscribed to EditorApplication.delayCall results in several seconds of added overhead because it's loading objects.
Editor versions tested: 2020.3.0f1 (first available), 2022.2.0a1, 2023.1.0a1, 2023.1.0a26
Tested using a 2019 MacBook Pro 16" i9/32GB
-
matiasges
Dec 19, 2023 13:56
Same Issue in Unity 2021.3.32
Since I added cinemachine is super slow to open my project and enter playmode. -
ClementSchepens
Jun 19, 2023 08:30
It seems linked to the number of timelines in the project. With near 1000 timelines I have a 27 seconds overhead when entering play mode and at every domain reload.
I’ve created 256 empty timelines and it added 14 seconds of overhead
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/SEQ-1436