Indexing takes a long time. . . . .
Answered
I have a huge project. It contains many files. I made packing of my project. After that, I opened the idea, and the indexing took 2 hours. What should i do to resolve this problem?
I'm already running out of patience
Thanks
Please sign in to leave a comment.
Please report an issue on YouTrack: http://youtrack.jetbrains.com/issues/IDEA attaching logs folder zipped ("Help | Show Log in..."). Do you face high CPU or Memory usage while indexing?
Hi, I had a similar problem with Windows. Before that, I tried to include a script that runs every time I started the terminal through create register value:
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun
and/or
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun
remove it solve the problem
What was this script doing? How did it affect the project indexing as IDE is not supposed to run the command line processor when indexing. Could you please try to reproduce it again and share the thread dumps via jstack for IntelliJ IDEA process when the indexing was slow? See https://intellij-support.jetbrains.com/hc/articles/206544899. You can upload your files at https://uploads.services.jetbrains.com/.
This script set some aliases. The indexing status bar disappears as usual (~15 sec), but this message appears approximately every 35 minutes.
Unfortunately, after the return of this script to autostart, the problem with indexing did not appear, but the IDE stopped authorizing me in the bitbucket (then the problem was also present) and began to require a password from the account, but I can not have it, because authorization is carried out through OAuth google. It is also noteworthy that at the same time it works perfectly through the git terminal.
P.S. had the same problems with both IDEA-U and WebStorm.
All sensitivity files are in uploads.services.jetbrains.com
IDE is using askpass.bat file to handle passwords in Git, so if you have a custom script that interferes with this process, git auth may not work properly. It's not related to the original indexing issue.