Intellij Idea Download Zip
Jacque Waiden
IDEA was working just fine for me several days ago, but one day, suddenly, it began hanging after opening a project, during the "Indexing" stage. I did not update IDEA and nothing changed about my projects. The IDE's UI hangs after it opens the project, with just a tiny little sliver of the progress bar for "Indexing" complete. Every 5-10 minutes or so it unfreezes and the progress bar crawls forward a little bit, before the IDE freezes again for another few minutes. This happens repeatedly for anywhere between 15 minutes and an hour, until it is finally finished indexing, at which point it hangs for another 5-10 minutes doing nothing, before it finally unlocks and allows me to develop.
While this is happening, my system is fairly unresponsive. Firefox tabs take a long time to switch, and scrolling in them is laggy. Opening a new terminal window takes a long time. Switching windows in general takes awhile. In htop, one of my CPU cores is loaded at 100% while the rest have a normal load, and about 6GB of RAM is used (fairly normal load when this system is idle.)
After consulting with a friend, I learned that on Arch Linux, systemd logs a dump of a process's memory every time a segfault occurs, except when a debugger is attached. strace is considered a debugger. Arch was thrashing my disks when it kept logging memory dumps due to all the segfaults, hence why the indexing was taking so long, because it was fighting for disk I/O.
I had this issue as well with version 2016.2 on Mac OS X. I had to do a force quit to end the application, then I deleted the .idea folder. The next time I launched IntelliJ everything worked fine. It had no problem indexing the project.
I was stuck with a similar issue with the latest IntelliJ Idea 2019.3, so maybe it'll help. For me the issue was with one of the plugins. Uninstalling, reinstalling, and cleaning caches didn't help. My steps were:
If step 4 above succeeds (which happened to me), one by one try enabling the plugins to see which one is causing error. For me it was Kubernetes plugin from JetBrains.
Relaunch the IDE (don't need to invalidate cache as that will cause it to start from scratch, whereas restarting from the point of failure, for me anyway, reported the problem file as soon as I restarted):
Our project doesn't use win32ole, so I moved the file to a safe location and restarted my IDE. Bingo, the problem was gone, and indexing finally completed after almost 1 year of effectively using Intellij as a slightly-smarter-than-notepad Ruby editor.
In my case I found out that Intellij is actually trying to index a 50GB directory with logs that was under the project's root. Make sure that if you have such a directory, it is marked as "Excluded" in the IDE.
You can see which file the IDE is indexing currently in the Indexing Status window (access by clicking on the indexing message in the toolbar). You may need to enlarge this window to see the full path of the file currently being indexed.
In PhpStorm, what solved this for me was excluding folders I didn't need to be indexed from the indexing (specifically the vendor folder, a caches folder, and a few asset folders that contained thousands of images). Instantly it began making progress and completed.
It seems that there might be several reasons for getting into this "indexing" hell. I spent a few hours trying to fix it using the ideas above.At the end of the day, with some profiling work, I found that the bad guy in my case was the CSV plugin: -csv-plugin
If you check the Intellij logs, which can be found under C:\Users\\.IntelliJIdea2019.1\system\log, you will get a pointer on what is failing. I was getting an error in Kotlin. After disabling the plugin and restarting Intellij, my issue was fixed.
I was all over SO, and even JetBrains' forums. I excluded directories via Project Structure Modules. I used Invalidate Caches And Restart on multiple occasions. I tried having only 1 project open to let it finish. I installed and tried 2019.2.4 and 2019.3.3 (the latter would crash for other reasons). And best of all, it only seemed to happen on one project!
It turned out, I had a TODO filter setup with a poorly-defined RegEx. It was something like \b.*wip\b.*; the idea was to find all of our "WIP" values. Well, the leading .* was a huge mistake and one that didn't occur to me until losing many hours blaming a plugin upgrade. I believe the reason this was a bad filter was because the project it was hanging on is in ExtJS, which is JavaScript, which means things are in triplicate with the app.js file and whatnot...
I was also facing the freezing issue with Intellij 2021.3. Earlier I was using Intellij 2021.1 version and that was working fine, but since I upgraded to Intellij version to 2021.3, it started freezing on indexing of files.
So, I went through the thread dumps available in the Intellij logs folder. After analyzing the logs, I found out that calls are blocking on the Package Search plugin. So, I disabled that plugin in Settings -> Plugin. To do that I had to pause indexing at the start for the time being. After disabling this plugin, it is working fine for me.
Invalidate Cache and Restart did not work for me on IntelliJ 2021.3 Ultimate.I was curious to see if the new Repair IDE feature on 2021.3 Ultimate version works on this issue on my mac.
I had the same problem with IntelliJ 2017.3.2. When I clicked on the indexing progress bar I noticed it was hung on a directory within my build directory. When I did a gradlew clean, which removed that directory, then the indexing was able to proceed.
I was using the Elm plugin and installed the elm-bounded-nats package which included a semi-large source file. IntelliJ kept hanging on this file, but did not always report this correctly in the indexing popover dialog (perhaps due to threading). When I exluded this specific file in Settings -> File Types ("Nats.elm"), indexing managed to complete successfully. Now the editor renders errors for this package, but the compilation process still works.
I tried all advices here but it has stuck right after opening the project. So I forcestopped it through task manager , removed project's .idea folder and then relaunched, it restored the .idea one , started indexing but this time I was able to mark as excluded vendor, bootstrap, storage/views folders and now it opens the project quickly as before
The top answers answers weren't working so I followed an IntelliJ forum recommendation to download Toolbox. From there the update from 2021.0.1 to 2023.3.2 went without a hitch. You can uninstall it after if you don't want another software manager on your machine
If you have a WebStorm (for example, version 2023.1), and it stuck on "Loading indexes" you can just "File -> Close project", then delete project from recent projects and again "Open" it. It worked for me.
If you enable the setting Use "CamelHumps" words in IntelliJ, commands like ctrl+left will go to the previous hump in camel case words, rather than the start of the word.For similar functionality in VS Code, enalbe the config intellij-idea-keybindings.useCamelHumpsWords under Settings.
However the "idea.vmoptions" file in the /bin directory is overwritten when idea runs.JVM options must be changed in the file with the same name, but in the configuration directory as JetBrains documentation states.This can be done following the instructions in the official documentation for idea and clion:
c80f0f1006