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

cd into folder really slow. #2885

Closed
masters3d opened this issue Jan 29, 2018 · 7 comments
Closed

cd into folder really slow. #2885

masters3d opened this issue Jan 29, 2018 · 7 comments

Comments

@masters3d
Copy link

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.16299.125]

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)

I am 'cd' into a big folder that lives on the windows side.

git version 2.15.1

find . -type f | wc:
15789 16064 1321131

It takes 1+ minutes to complete operation.

  • What's wrong / what should be happening instead:

It is way too long. Other folders 'cd' are almost instant.

  • Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here)

Not sure how to stance built in command 'cd'

@masters3d
Copy link
Author

Closing. This seems to only happen the first time you switch into a big folder with a ton of files

@masters3d
Copy link
Author

Nope. This comes back after closing the bash window.

@masters3d masters3d reopened this Jan 29, 2018
@masters3d
Copy link
Author

Sometimes control + c allows you to see the target folder

@masters3d
Copy link
Author

Seem to only manifest when running in Legacy mode

>wslconfig.exe /list
Windows Subsystem for Linux Distributions:
Legacy (Default)
Ubuntu

@xarthurx
Copy link

I also notice that when opening a large file for the first time, it is very slow.
Opening again while the bash.exe is open will be fast.
But once the bash.exe is closed and re-open again, everything start again. (opening for the first time will be painfully slow.)

@masters3d
Copy link
Author

sad state of things. I was hoping to use bash for all git related things but Mubarak’s repo is really big. I am forced to use git windows.

@therealkenc
Copy link
Collaborator

#981 and #873 are the landing zones.

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

3 participants