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

Repeated hangs after subdirectory has over 4760 files #6188

Closed
cyberduck opened this issue Sep 1, 2011 · 2 comments
Closed

Repeated hangs after subdirectory has over 4760 files #6188

cyberduck opened this issue Sep 1, 2011 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 1, 2011

34d104f created the issue

The application (4.1.2) has started to hang when one sub directory on logged-in server exceeded 4760 files. The problem appears faster (within a few minutes) if the large directory is viewed, but eventually (within 5 minutes) it hangs in any directory on the server. It is also difficult to add any more files to this large directory. After all files are sent the applications hangs while "Listing directory xxxx". see the log drawer below.

TYPE I
200 Switching to Binary mode.
PORT 192,168,1,51,201,179
200 PORT command successful. Consider using PASV.
STOR /var/www/graphics/chip/1970chevcanada_19.jpg
150 Ok to send data.
226 File receive OK.
QUIT
221 Goodbye.
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2011

@dkocher commented

Could this be a duplicate of #6183 instead? Do you have the option Transfers → Remove when transfer completes in Preferences enabled?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 4, 2011

@dkocher commented

In ec1b640.

Loading

@cyberduck cyberduck closed this Sep 4, 2011
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant