This problem only started showing up in 5.2.0p1, and I suspect it's related to this change: "(715960) - Version Control: Do not use cached status for checking editability in VCS." In 5.2.0p1, any time you select any version-controlled asset (i.e. anything in your Project tab), the editor immediately becomes unresponsive (on Mac, it beachballs). If you look at the p4plugin.log file, it shows that P4 is spamming the fstat command for the asset you just selected: "fstat "[path]/Assets/Scripts/PopulateResolutionDropdown.cs.meta" That message repeats over and over and over, during which time the editor is completely frozen. If you click around in the frozen editor to deselect the asset in the Project tab, the click will eventually get through on Mac and quit the beach-balling, but that doesn't appear to work on Windows. On Windows the freeze is unrecoverable. In short, the nonstop fstat commands make the 5.2.0p1 editor completely unusable in a project that uses P4 for version control. Reported as #728723.