Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.3.0a1
2019.3.10f1
2020.1
2020.2
Issue ID
1239162
Regression
Yes
[Performance Regression] "EditorOnly [Prefabs.MergePrefabs]" process noticeably slower when opening a scene
Reproduction steps:
1. Import the attached .unitypackage ("1239162.unitypackage")
2. Open the Scene "Candy Trip 3"
Expected result: Scene is opened at the same speed as before
Actual result: Scene takes a lot longer to open than before
Reproducible with: 2019.3.0a1, 2019.3.12f1, 2020.1.0b8, 2020.2.0a9
Not reproducible with: 2018.4.22f1, 2019.2.0a14
Notes:
- In the versions deemed not reproducible the same action would take about 90-100ms, while in the versions deemed reproducible it would take 25000-50000ms
-
slippyfrog
Oct 10, 2024 19:29
Additional notes here from others who have observed the issue:
The issue really cuts down on rapid iteration time.
-
slippyfrog
Sep 26, 2024 20:00
In unity 2022.2.47 Prefabs.MergePrefabs takes 7s-8s when entering play mode.
-
JofreMP
Nov 30, 2022 13:23
It happens de same to me in the version 2020.3.11f1, so the bug is still not fixed on that version.
-
Bastienre4
Aug 19, 2020 15:24
In my case, in some maps, it takes more than 60s to "Prefabs.MergePrefabs" on play mode exit.
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
- Pickers and ‘+'/’-' buttons are not visible on the right side of parameter fields when the width of the "Project Settings... -> Quality" window is small
- "AssertionException: Assertion failure. Value was False" error is thrown when unmaximizing a docked UI Builder Window
- INVALID_ENUM warning is thrown in WebGL Player when building an empty scene
- Crash on ApiGLES::ClearBufferSubData when running the Player a second time on Meta Quest 2
- "Process VFXCamera Command" column is displayed in the "Render Graph Viewer" when there are no VFX in the Scene
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.8f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.24f1