Intellij IDEA won't start

Question

When I open Intellij 14 , it starts the initial loading and then following is shown in the screen.After that it is vanished and program does not start.

But when I open the task manager it is shown in the Processes as per the below figure.

Sometimes the program starts after about 10 minutes .Sometimes it won't start at all.Can someone give me a solution on how to overcome this problem ?

Answer 1

C:\Users\<user>\AppData\Roaming\JetBrains\

if you are a Windows user, remove this directory. It helped me

Answer 2

Had a similar issue.

idea64.exe just didn't start silently.

idea.bat printed just IDE is being shut down and didn't start either.

In my case there was no effect of manipulations with idea64.exe.vmoptions, but it helped to find and kill from Task Manager an invisible orphan idea64.exe process.

This solution was hinted by the first comment by @CrazyCoder at https://intellij-support.jetbrains.com/hc/en-us/community/posts/360009511720--Solved-Idea-Community-doesn-t-start-after-update-to-2020-1-4.

Answer 3

For me, the cause was a bad plugin.

I moved all plugins in below directory to a backup directory, and started IDEA, and it started without an issue.

C:\Users\<username>\AppData\Roaming\JetBrains\IntelliJIdea2021.2\plugins

Then, copied plugins back to the above directory one by one, to identify the broken plugin.

Answer 4

You can try to open Intellij on CLI.

cd C:\Program Files\JetBrains\IntelliJ IDEA 2020.1\bin

later then execute this command

idea.bat

Probably Intellij will open. If it will not open then you can see the error message why it will not open on CLI.

Answer 5

Just updated IntelliJ to a newer version, and I followed the 'configure' link to double the memory used for IntelliJ which I later regret. IntelliJ could not restart. Open the system.log (e.g. Use CMD+SPACE_BAR and search 'console' on MacOs, then go to system.log), I can see IntelliJ aborted a few times with an abnormal code 1. Here the lines related to the launch,

Processing VMOptions file at 
 /Users/[user]/Library/Preferences/IntelliJIdea2019.2/idea.vmoptions
com.apple.xpc.launchd[1] (com.jetbrains.intellij.22016[2971]): Service exited with abnormal code: 1

I can see the path from where IntelliJ loads vm options during the launch. Checking the bin/ of my IntelliJ application, I can see another version of the idea.vmoptions file that has a slightly older timestamp. By comparing the content of the two files, I now realized that IntelliJ created another vm option file that has only a sub set of options in a newer location which broke the restart. Deleting or just safely renaming the newer file in the [User] sub directory fixed my problem.

Answer 6

Following steps helped me to overcome the Java heap size related issues on InteliJ IDEA.

Go to the location where you have installed the IDEA IDE and search for the following file:

idea64.exe.vmoptions

Change it accordingly.

-Xms4196m
-Xmx8092m
-XX:MaxPermSize=1000m
-XX:ReservedCodeCacheSize=1024m
-ea
-Dsun.io.useCanonCaches=false
-Djava.net.preferIPv4Stack=true
-Djsse.enableSNIExtension=false
-XX:+UseConcMarkSweepGC
-XX:SoftRefLRUPolicyMSPerMB=50

Also be aware of the 32-bit address space limit on Windows which makes it hard to use heap sizes higher than 750m. Should you need to use larger heap, make sure to switch to the 64-bit JVM first, otherwise IDE may crash on start or start to crash randomly during work.

Answer 7

Check the logs for error or issue in the path C:\Users\.IntelliJIdea14\system\log\idea.log.

If that report HeapDumpOnOutOfMemoryError

Go to VM options files in the path C:\Program Files\JetBrains\IntelliJ IDEA 2018.2.6\bin

Increase the -Xms750m to greater value say -Xms900m .

That solve the issue for me

Answer 8

Just like Tom, I too have increased the memory when IntelliJ asked and regretted it. This is the screen that asked for it:

However, in my case, instead of editing the .vmoptions files in the bin folder, IntelliJ created a new one in my home directory which I can only assume overrides the ones in the bin folder. I would assume this is typical of the new versions - I am using IntelliJ 2016.1 right now.

So, in order to fix this issue, go to C:\Users\<your_username>\.IntelliJIdea<version>\config (or your OS' equivalent) and delete the idea.exe.vmoptions and/or idea64.exe.vmoptions file from there. This should remove the override and have IntelliJ use the settings in the bin folder.

It might be worth checking the files in the bin folder as well, in case IntelliJ changes how it handles these settings.

---

Here are the default .vmoptions files in the installation's bin folder; you can't delete these as it will prevent IntelliJ from starting:

bin/idea.exe.vmoptions:

-server
-Xms128m
-Xmx512m
-XX:MaxPermSize=250m
-XX:ReservedCodeCacheSize=150m
-ea
-Dsun.io.useCanonCaches=false
-Djava.net.preferIPv4Stack=true
-Djsse.enableSNIExtension=false
-XX:+UseConcMarkSweepGC
-XX:SoftRefLRUPolicyMSPerMB=50

bin/idea64.exe.vmoptions

-Xms128m
-Xmx750m
-XX:MaxPermSize=350m
-XX:ReservedCodeCacheSize=225m
-ea
-Dsun.io.useCanonCaches=false
-Djava.net.preferIPv4Stack=true
-Djsse.enableSNIExtension=false
-XX:+UseConcMarkSweepGC
-XX:SoftRefLRUPolicyMSPerMB=50

Answer 9

Edit C:\Program Files (x86)\JetBrains\IntelliJ IDEA 15.0.6\bin\idea.exe.vmoptions the Xmx to Xmx512

-server
-Xms128m
-Xmx512m

Answer 10

You might also check your IDEA_JDK_64, JAVA_HOME and JDK_HOME environmental variables. In my case I updated Java version and deleted previous directory containing JDK. Then IntelliJ started to dissapear from processes just a few seconds after launch. I changed all paths to point proper JDK directory and then it started to work as it should.

Answer 11

I got an out-of-memory dialog on intellij 15 and took an option on that dialog to increase max memory. Thereafter I could not start intellij. So, I looked in the intellij /bin folder for a pid file (per another stack overflow question) to see what was happening, but I could not find one. There was however a file (idea.exe.vmoptions) that had changed (to hold my new memory setting). So I edited that file to set max memory back to what I had before, and now it works.