Search Issue Tracker
Won't Fix
Won't Fix 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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Not caused by Perforce
Resolution Note (2023.2.X):
Not caused by Perforce