Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2019.2.0a11
Issue ID
991427
Regression
No
[VCS] Version Control window being open makes slows things down when doing multiple VC Tasks in a row
To reproduce:
1. Open attached project (attached by QA);
2. Make sure you are connected to Perforce (Edit > Project Settings > Editor > Version Control);
3. Press Story > Episodes > Test Checkout Episodes Normal Checkout;
4. Open the Console and see the Debug.Log;
5. Open Version Control Window (Window > Version Control);
6. Repeat 3rd and 4th steps.
Expected result: Editor does not hang when checking out files with Perforce and Version Control window is open.
Actual result: Checking out files with Perforce takes significantly more time when Version Control window is open.
Reproduced on versions: 5.5.6f1, 5.6.5p1, 2017.1.3f1, 2017.2.1p2, 2017.3.0p3, 2018.1.0b4.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2020.1):
The checkout performance with the VCS window open has improved 2x and should now be a lot closer to that of not having the window open.
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.16f1