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

Traversing folders seems to be a problem #44

Open
SF-Simon opened this issue Dec 21, 2017 · 4 comments
Open

Traversing folders seems to be a problem #44

SF-Simon opened this issue Dec 21, 2017 · 4 comments

Comments

@SF-Simon
Copy link

let folders = Array(try Folder(path: "/xx/xx/").makeSubfolderSequence(recursive: true, includeHidden: false));

This is the swift code, I'm not running in the main thread main, and when my files are less, it's no problem. But if I have more files (about 150), there will be a problem, and Xcode directly locate the error.

CurrentChildIterator = childIteratorQueue.removeFirst()

I can't understand what this is, and I hope to be able to get the solution.

@clayellis
Copy link
Contributor

@DiVeNLee what seems to be the problem? Like what happens when you have > 150 files? And are you talking about 150 directories (nested or un-nested) or just files?

@SF-Simon
Copy link
Author

@clayellis
I'm sorry, my English is very bad. I try to describe it again.

About 150 files are not folders. These files are very messy, there is no fixed structure, but most of them are in the same sub folder, and there are other folders under this folder.
But it's strange that I traversed all the files, and it won't go wrong, only when I traversed all the folders.

@clayellis
Copy link
Contributor

@DiVeNLee no worries, I'm sure I'm not very good at your native language! (Unless it's French...)

So when you traverse all of the files you see the files you expect, correct?

But when you traverse all of the folders, some of the folders are missing?

@SF-Simon
Copy link
Author

@clayellis
No, it's crash, and the application has not been able to run again. And Xcode jumped directly to the position I said

CurrentChildIterator = childIteratorQueue.removeFirst()

This is within the Files

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

No branches or pull requests

2 participants