Search Issue Tracker
Fixed
Fixed in 2021.3.40f1, 2022.3.35f1, 6000.0.7f1
Votes
1
Found in
2021.3.37f1
2022.3.19f1
Issue ID
UUM-70391
Regression
No
The Editor hangs when opening a project that uses local packages and Version Control
How to reproduce:
1. Open the “IN-74168_repro“ project
2. Navigate to Edit → Project Settings → Version Control
3. Set up Perforce
4. Close the project and open it
Expected result: The Editor opens quickly
Actual result: The Editor hangs and looks white
Reproducible with: 2021.3.37f1, 2022.3.19f1
Could not test with: 2023.2.19f1, 6000.0.0b16 (could not resolve errors)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
CamouflajColin
Apr 24, 2024 16:35
If it's not apparent in the ticket report, the issue is because the version control plugin does an FSTAT on all files in the packages and project settings directory. Probably to catch assets not tracked by the asset database (packages-lock, manifest, etc) and therefore outside of normal version control flow. However, packages that are source visible and versioned in the Packages directory can be very large (visual scripting, render pipelines, etc.) AND are generally managed by the asset database as well. The FSTAT operation on thousands of files can cause the editor to take many minutes to open. It should not stat these files.