-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
Round Number Delay When Starting Under WSL #1831
Comments
Originally posted by @pedro2d10 in #549 (comment)
Here the following logs:
As you can see, there 60s between I hope this will help |
The round numbers hint at possible timeout from the OS. There is no configurable timeout. Wrapping and profiling could confirm. |
@pedro2d10 error handling has been improved and more profiling has been added. I would be most grateful if you could test again. |
Here the new logs:
On line 15, there is exactly a 60s delay befaore it goes to the next step. |
Thanks @pedro2d10 I've attempted replication with a dummy directory populated after After cleaning: 40,41c40,41
< [profile] END explore init /path/to/nvim 60288ms
< [profile] END core init /path/to/nvim 60289ms
---
> [profile] END explore init /path/to/nvim 1ms
> [profile] END core init /path/to/nvim 1ms
43c43
< [profile] END view open 11ms
---
> [profile] END view open 2ms |
There's a lot of file system operations taking place to detect whether a file is executable:
@pedro2d10 I would be most grateful if you could test with a branch that removes this check: cd /path/to/nvim-tree.lua
git pull
git checkout 1831-test-skipping-executable-check Possible actions:
|
@alex-courtis you're a genius! It work great now. There's no delay when nvim-tree open. Let me now if you want me to send you come log or change parameters. |
@doanamo I would be grateful if you could take a look at this one: I don't have a windows machine so I cannot investigate. |
I do not know whether powershell/msys executable detection works either, which uses a different codepath. The wsl code is buggy and is expensive, making many FS calls. This is the only WSL specific codepath. Other windows codepaths are needed:
We don't have the expertise or means to test these windows specific codepaths. I would like to remove executable flag functionality under windows. @gegoune ? |
I don't have ability to test windows either. Unless someone steps in and offers help I think removing that single functionality isn't big problem. Will just need a small info that this functionality is not available on that platform. |
Good call. |
Multiple WSL users have reported issues with a freeze on startup, always a round number: 20s, 100s, 60s
Git enabled 20s: #1719
Git disabled 60s/100s: #549 (comment)
The text was updated successfully, but these errors were encountered: