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
- Crash on SpriteAtlas::PopulatePackedTexturesAndRenderData when changing Import Settings on a Sprite that has been added to a Sprite Atlas while in PlayMode
- Empty lists can be applied in Additional Compiler Argument list in Project Settings
- [Vulkan][OpenXR] SRP Foveation Regions Not Centered when eye-tracking is not used
- Long Color Library name overflows outside input field bounds
- Shader Graph validation and Metal threadgroup memory warnings thrown when installing HDRP package in Universal 3D Template
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