Search Issue Tracker
Fixed in 5.3.0
Votes
9
Found in
5.2.1f1
Issue ID
730014
Regression
Yes
[Version Control] Perforce & Plastic SCM plugins cause Editor slowdown
Steps to repro
1) Set up Perforce server on network (Plastic SCM not tested)
2) Set up Perforce client (P4V) on local machine, connected to server
3) Download project from this bug, unzip
4) Add relevant files (Assets folder, ProjectSettings folder) to depot in P4V (no need to commit)
5) Open project in Unity 5.2.0p1 or greater
6) Open Version Control window
7) Connect to Perforce server
8) Open only scene in project
9) With nothing selected in Project window, observe Editor framerate is fine
10) Select an asset so it appears in Inspector
11) Observe framerate/responsiveness of Editor is greatly reduced when navigating in Scene window, and lots of console spam is produced
Comments (3)
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
- Broken hyperlink formatting in HDRP 3D Sample Tutorials
- Missing spaces in High Definition 3D Samples Template Tutorials
- Win64 CPU is set to None when applying changes to plugin where the meta has the serializedVersion 2
- Sprite Atlas textures from all included build scenes persist in Editor memory when building the Player
- Disabling all columns in Light Explorer throws “ArgumentException” error in the Console window
rpopic2
Apr 25, 2018 07:45
This is also happening to me
AnthonyReddan
Feb 26, 2018 23:11
This is happening again.
csr247
Oct 03, 2015 05:26
The p4plugin.log file shows that Perforce is spamming the fstat command. See here:
http://forum.unity3d.com/threads/5-2-0p1-p4-version-control-hangs-editor-due-to-fstat-spam-bug.355906/#post-2315625