I created one (the same contents as ) and it all seems to work now.īefore doing this though, in case it helps you resolve this for others, here is the contents of my idea.log (there was nothing in todays threaddumps-XXXX directory either): But, interestingly, there was no in my bin directory. This was a clean install, Windows wasnt virtualizing anything. Mostly, I hope others have better luck with idea64.exe. Part of me hopes others will see the same behavior so we can know it's not just my configuration. I'm going to kill the process and go back to launching it with the batch file which works without any of these issues. Ten minutes in and IDEA still hasn't started completely. My workstation has 24GB of RAM, so even a 5GB allocation is ok, though probably excessive for my project needs. Interestingly, I noticed the status bar showed the Xmx memory allocated for the IDE as 5459M, even though the contains the following: Every couple of minutes, the window disappears, then reappears, but the progress bar doesn't move. A CPU meter widget shows some activity on multiple cores, so I let it run. It started without that error, but its "Loading project" startup process just churns on after the initial indexing process.
(I think the OS X installer, or maybe its IDEA itself, does ask whether 32-bit or 64-bit JDK is to be used.)īased on your info, I set both JDK_HOME and IDEA_JDK = C:\swdev\Tools\Java\64bit\jdk1.6.0_23. Then the installer can set whatever environment variables need to be set. I'd like to suggest the installer be modified to ask if 64-bit JDK is to be used and allow its location to be specified during install. The error dialog said the JDK defined by EXE4J_JAVA_HOME was not 64-bit, so naturally I should have interpreted that to mean either JDK_HOME or IDEA_JDK needs to be set.
>So, in order to run under 64-bit JDK you must have one of the above environment variables defined and pointing to the 64-bit JDK installation directory.
0 kommentar(er)
