Perforce Public Knowledge Base - P4V is hanging
Reset Search



P4V is hanging

« Go Back



P4V is not responsive but equivalent commands respond well from the command line

First run the equivalent command from the command line.  Enable P4V logging through P4V, Edit, Preferences, General, Show p4 reporting commands, Show p4 command output for file operations, and Enable logging to file.   This will show what command is not responding.  Try the same command from the command line.  On Windows, open a command prompt and run
p4 set P4USER=user name
p4 set P4PORT=server:1666
p4 set P4CLIENT=P4V workspace name
Then run the command in the log pane (or as much as you can if the command shows {x more items}).

The P4V client may be slower than the command line client because of application issues. Most likely the problem is due to P4V running additional commands such as "p4 fstat" or "p4 dirs" that provide information to the graphical interface.  To diagnose the problem, try the following.

  1. Check machine resources

    Check CPU and memory using Task Manager on Windows or the "top" command on Unix.  If the system is out of resources, change the P4V preference settings to use fewer server resources.   Go to P4V, Edit, Preferences, Connection and set the parameters as follows:
    Check server for updates every 15 minutes
    Maximum number of files displayed per changelist 100 
    Maximum size of files to preview 1000 KB
    Number of changelists, jobs, branch mappings or label 
    to fetch at a time: 100
  2.  Look at the P4V log

    View the log and look for any errors or continually repeat.
  3. Create a new client workspace
    Create a simple client workspace with the client root on a local hard drive and try to reproduce the problem.  This will isolate issues with a particular client.  Or the "p4 fstat" and "p4 dirs" commands may be encountering protection errors and attempt to look for files not in the client view which may slow down refreshes.
  4. Isolate network issues

    Create a new client workspace on the Perforce server.  Make sure the client root is on the server's local hard drive to be completely independent of the network. Try to reproduce the problem using this client workspace.  Then try P4V on machines further away from the server. Tests may show that one subnet is slow but others are fast.  Another approach is to run Wireshark or strace to determine where network access is slow or if packets are being retransmitted or dropped.
  5. Check that MD5 digests exist and are updated

    You may see that the P4V log shows "running p4 -ztag fstat" but that this command does not complete.  Additionally, "corrupted during transfer (or bad on the server)" errors may be seen.  This can occur because the transfer of data between the client and server is now verified against corruption as seen in our release notes.

    To speed this process, update files without md5 digests by running "p4 verify" as follows:
    p4 verify -qu //...
    This should not be necessary in most cases.
Related Links



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255