Search Issue Tracker

Fixed in 2018.1.X

Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X



Found in


Issue ID




[Version Control] Perforce sending fstat commands and freezing editor with poor internet connection

Version Control


Steps to reproduce:
1. Set up a perforce server and enable integration on Unity on any project
2. Create a handful of files (new scripts for example)
3. Download "" app attached
4. Open and check Lag, set it to about 200-500 ms (The more you set it the more visible it is) and start
5. Now, most of the time, when you click on a file in your project an fstat command will be issued which will freeze the editor until it completes
6. You can also move focus from the editor to another window and back to make the fstats appear again, if they stop

Expected result: The editor does not freeze except when saving, or doing explicit version control operations
Actual result: Editor freezes on fstat command and becomes unusable when it happens a lot in sequence

Reproduced on:5.6.0f1, 5.6.2p1, 2017.1.0f2
Regression introduced in: 5.6.0b10
Not reproduced on: 5.5.4p1, 5.6.0b1, 5.6.0b8, 5.6.0b9

Note: Bug only appears if your inspector is active. Possibly caused by "IsOpenForEdit" call of the Inspector.

Comments (4)

  1. StevenHutton

    Jan 22, 2020 14:31

    Seeing this issue or a similar hanging issue when perforce is connected in 2019.2.6f1

  2. CoSpinu

    Mar 21, 2019 08:40

    I'm using 2018.3.7f1 and i had a similar behavior. It got unfrozen once i managed to close the inspector window, so i suppose it's the same problem

  3. DavidLFunkitron

    Jan 11, 2018 18:57

    I am still seeing this issue reproduce, in Unity 2017.3.0f3.

  4. wightwhale

    Nov 20, 2017 23:57

    I'm getting this issue on my LAN based server as well.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.