Search Issue Tracker
Won't Fix
Under Consideration for 2021.3.X, 2022.3.X, 2023.1.X
In Progress in 2023.2.X
Votes
0
Found in
2020.3.42f1
2021.3.14f1
2022.1.23f1
2022.2.0f1
2023.1.0a21
2023.2.0a1
Issue ID
UUM-20162
Regression
No
[Perforce] VersionControl.Task.Wait makes Editor unresponsive for a long period when performing default VCS actions
How to reproduce:
1. Open the attached “My project” project
2. Connect it to Perforce server
3. Open the Profiler to measure the time of the next step in the Editor
4. Move the file contents from “Assets → FirstFolder” to “Assets → SecondFolder” in the Project Browser
Expected result: Editor becomes unresponsive for 4 seconds
Actual result: Editor performs the actions in less than a second
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a21
Reproduced on: macOS 13.0 (Intel)
Note:
- First time reverting took ~2 minutes to wait
- In the user’s project, it takes ~5 minutes to wait for each action
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
Not caused by Perforce