atom freeze after update 2.1.0 in Windows 10

[KamiGim]

No description provided.

[saschagehlich]

@KamiGim Please provider some more information:

• How large is the project you're using?
• Does your project use git?
• When exactly does atom freeze?

[KamiGim]

1. not large I guess
2. yes I use git
   

[saschagehlich]

This module doesn't lock up for no reason, I believe the project you're working on doesn't look huge, but it is pretty large. Do you have folders like node_modules or bower_components that contain large amounts of dependencies and are not in .gitignore?

[KamiGim]

No node_modules is in .gitignore

but if I use this version,it works fine

[saschagehlich]

Are you opening a folder that contains multiple git directories instead of opening a single git directory? In this case atom does not recognize the git-subdirectories and does not ignore files and directories in .gitignore. Therefor, all files and directories in node_modules are being indexed, resulting in a freeze.

[KamiGim]

yes I open two project folders
right now I also try to open only one folder. it still freezes
maybe I should use older version instead

[ddirks]

Similar problem for me on Win 10 Pro x64, even when opening my user account Atom config folder/project, which is not large. I got the "Rebuilding paths cache" message in the lower right corner, and then the "Editor is not responding" error dialog. I tried the "Keep Waiting" option five times to be sure it wasn't just thinking really hard about something, but I finally had to "Force Close." Restarting Atom put it right back into the unresponsive "Rebuilding paths cache" state.

To get out of the loop, I first tried manually deleting the ~/.atom/packages/autocomplete-paths directory. On restarting Atom, I still saw the "Rebuilding paths cache" message and the editor was still unresponsive, giving the same error dialog. Next, I restarted Atom with the --clear-window-state flag, which allowed the editor to start normally.

Finally, thinking that the --clear-window-state might have cleared up whatever the problem was, I tried reinstalling autocomplete-paths again. Sadly, I saw the same behavior after the second install, and had to do another cycle of delete & clear.

[saschagehlich]

I have just released 2.2.0 which sets a file limit (2000 by default). Please check it out.
If you get the message Maximum file count exceeded, then for some reason atom is not recognizing ignored files. I've added a troubleshooting guide to our wiki.

[jlowin]

@saschagehlich I came here looking for why that 2000 message popped up. In my case I know it's because I have a project folder that contains multiple git repos, one of which has a node_modules folder.

However, my Atom locks up despite displaying the 2000 message warning. By disabling/reenabling the extensions, I can confirm that autocomplete-paths is the cause of the freeze. So for what it's worth, the message is informative but doesn't seem to be preventing the core issue.

I never experienced this freeze until this morning when I updated to the 2.X branch. I haven't gone through the code except at a high level, but perhaps some new feature is much more computationally expensive with large projects than it would appear to be?

[dhawton]

Just updated.. not getting that message but same symptoms.. and now I'm stuck.

[saschagehlich]

@jlowin Thanks for reporting this. I'll have access to a windows machine tomorrow and will look into this.

[linjialiang]

me too， This issue is caused by a conflict with [email protected]？

[linjialiang]

autocomplete-paths 2.5.0
There is still no completion path complement

[linjialiang]

Community Packages (30) C:\Users\kc_em.atom\packages
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[jlowin]

@saschagehlich thank you! I did not read the title of this issue closely enough; I am actually using a Mac.

[saschagehlich]

You could try adding node_modules to your ignored names core setting

…

On Aug 13, 2017 1:49 PM, "Jeremiah Lowin" ***@***.***> wrote: @saschagehlich <https://github.com/saschagehlich> thank you! I did not read the title of this issue closely enough; I am actually using a Mac. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#118 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHThO1M94fCfxh44AsjCLlD9BNHPDT1ks5sXuLKgaJpZM4O1BkP> .

[jlowin]

That did it, thanks! I sort of assumed it was in there by default to be honest.

[saschagehlich]

I was able to reproduce the issue on Windows 10 and will investigate

[saschagehlich]

Apparently the many pathwatchers are causing this

[saschagehlich]

Due to limitations in the Windows implementation of node-pathwatcher I disabled path watching for Windows in 2.6.0. This fixes the freezing issues.

[KamiGim]

cool thanks It's working now

[ddirks]

Here's a data point with the 2.6.0 version (Win 10 x64): I installed and opened a large project and got the "Maximum file limit of 2000 files exceeded" (as expected, I suppose.) In addition, I also continued to see the "Rebuilding paths cache" message on the status line. Interestingly, this message did not permanently block other operations in the UI (as it did previously with the 2.1.0/2.2.0 versions), but it was obviously running. (Switching between tabs would take 10+ seconds, for example.)

So: no --clear-window-state required to recover, but still unusable (for me) with autocomplete-paths 2.6.0 installed.

Is it possible that the "Rebuilding paths cache" state is persisting somewhere even when the package is uninstalled/reinstalled?