Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EditItem times out if multiple other workspaces have the file open #73

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Open the file for edit in a large number of workspaces. The current 
reproducible case I have for this is 40 workspaces, but it probably happens for 
fewer.
2. From Visual Studio, try to open the file for edit. Happens if either I right 
click on the file's tab and select EditItem, or try to save the file with 
autoCheckoutOnSave

What is the expected output? What do you see instead?
I expect the file to be opened for edit. This is printed in the output pane:
NiftyPerforce ( Info): p4.exe: edit [FileName] timed out (30000 ms)

What version of the product are you using? On what operating system?
1.3.7, VS2008

Please provide any additional information below.
If I open the file for edit from Windows Explorer, there is a very large 
warning consisting of lines of the form
"[Filename] - also opened by [WorkspaceName]'
My guess is that the process times out when these warnings get over a certain 
size.

Original issue reported on code.google.com by [email protected] on 14 Nov 2011 at 7:16

@GoogleCodeExporter
Copy link
Author

This was also happening in version 1.3.1.

Might be fixed by the change in r130.

Original comment by [email protected] on 14 Nov 2011 at 7:29

@GoogleCodeExporter
Copy link
Author

Yeah, sorry about that. I realized that if the perforce command has too much 
output then the output handling from before r130 will always hang in a 
deadlock. Which reminds me, I should make a new version with this code.

Original comment by [email protected] on 14 Nov 2011 at 7:49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant