Search Issue Tracker

Fixed in 2022.1.X

Planned for 2021.3.X

Votes

0

Found in

2022.1.0a4

Issue ID

1355830

Regression

Yes

Regression in time taken to enter Play Mode caused by asset database change

Asset - Database

-

The time taken to enter play mode in the Lost Crypt project regressed from 4.6 to 4.8 seconds when PR was merged:

https://ono.unity3d.com/unity/unity/pull-request/128606/_/assetpipeline/postprocessallassets-in-asset-db-ready-state

https://observer.cds.unity3d.com/project?projectID=LostCrypt&test=PlayModeTests&sample=EnterPlayMode.SubsequentTime&changeset=1e9ee699d803&pivot=editor&pinVersions=false&editorBranch1=trunk&projectBranch1=master&fromVersion1=2021-06-10T01:47:51Z&toVersion1=2021-08-03T10:02:00Z&color1=eb144c

Steps to reproduce:
1. Download and open the project "LostCrypt.zip"
2. Go to Window > General > Test Runner
3. In EditMode, click on TestEnterExitPlayMode
4. Click on Run Selected
5. Wait for the Test to complete

While investigating this, it was also found that the time to enter play mode is significantly slower the first time to subsequent times. This should maybe be raised as a separate bug:

Expected result: The time taken to enter/exit Play Mode for the first time is approximately the same as the time taken by subsequent entries/exits
Actual result: The time taken to enter/exit Play Mode for the first time is significantly longer than the time taken by subsequent entries/exits

Reproducible with: 2022.1.0a4, 2022.1.0a5
Not reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b8, 2022.1.0a3

Note:
The number of iterations for the test can be changed in line 40 in Assets/Tests/EditModeTests/PlayModeTests.cs. By default it is 25

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.