Start of IntelliJ Idea in 64bit mode fails with plugin installed
https://youtrack.jetbrains.com/issue/IDEA-150623
java.lang.Error: The filename, directory name, or volume label syntax is incorrect.
at com.sun.jna.Native.open(Native Method) at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:171) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:398) at com.sun.jna.Library$Handler.<init>(Library.java:147) at com.sun.jna.Native.loadLibrary(Native.java:412) at com.sun.jna.Native.loadLibrary(Native.java:391) at turboactivate.TurboActivateNative.<clinit>(SourceFile:1113) at turboactivate.TurboActivate.PDetsFromPath(SourceFile:893) at com.illuminatedcloud.intellij.license.LicenseValidator.<clinit>(SourceFile:50) at com.illuminatedcloud.intellij.parser.ApexParserDefinition.<init>(SourceFile:38) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.picocontainer.defaults.InstantiatingComponentAdapter.newInstance(InstantiatingComponentAdapter.java:193) at org.picocontainer.defaults.ConstructorInjectionComponentAdapter$1.run(ConstructorInjectionComponentAdapter.java:220) at org.picocontainer.defaults.ThreadLocalCyclicDependencyGuard.observe(ThreadLocalCyclicDependencyGuard.java:53) at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.getComponentInstance(ConstructorInjectionComponentAdapter.java:248) at com.intellij.util.pico.ConstructorInjectionComponentAdapter.getComponentInstance(ConstructorInjectionComponentAdapter.java:59) at com.intellij.openapi.extensions.AbstractExtensionPointBean.instantiate(AbstractExtensionPointBean.java:75) at com.intellij.openapi.extensions.AbstractExtensionPointBean.instantiate(AbstractExtensionPointBean.java:68) at com.intellij.openapi.extensions.AbstractExtensionPointBean.instantiate(AbstractExtensionPointBean.java:63) at com.intellij.openapi.extensions.CustomLoadingExtensionPointBean.instantiateExtension(CustomLoadingExtensionPointBean.java:47) at com.intellij.lang.LanguageExtensionPoint.access$000(LanguageExtensionPoint.java:28) at com.intellij.lang.LanguageExtensionPoint$1.compute(LanguageExtensionPoint.java:42) at com.intellij.openapi.util.NotNullLazyValue.getValue(NotNullLazyValue.java:39) at com.intellij.lang.LanguageExtensionPoint.getInstance(LanguageExtensionPoint.java:53) at com.intellij.openapi.util.KeyedExtensionCollector.buildExtensions(KeyedExtensionCollector.java:154) at com.intellij.openapi.util.KeyedExtensionCollector.buildExtensions(KeyedExtensionCollector.java:127) at com.intellij.openapi.util.KeyedExtensionCollector.forKey(KeyedExtensionCollector.java:115) at com.intellij.lang.LanguageExtension.forLanguage(LanguageExtension.java:56) at com.intellij.psi.stubs.CumulativeStubVersion.getCumulativeVersion(CumulativeStubVersion.java:36) at com.intellij.psi.stubs.StubUpdatingIndex.getVersion(StubUpdatingIndex.java:228) at com.intellij.util.indexing.FileBasedIndexImpl.a(FileBasedIndexImpl.java:393) at com.intellij.util.indexing.FileBasedIndexImpl.a(FileBasedIndexImpl.java:296) ... 35 more
Comments (8)
-
repo owner -
reporter java used for launching is 64bit, native code library name is different and fails to load. you can also ask the used at IJ tracker :)
-
repo owner Thanks, Maxim. I've commented on the IJ issue and will follow up with June.
-
Ha. We meet again! This is a lower-priority issue for me, especially since the OST magically loaded last night even with 32bit.
I'm just clicking the idea64.exe to run this. I have an older version of Java (7.0.670.1) living in my Windows/System32 folder, which if I'm remembering correctly I needed to have for Eclipse with the Force.com IDE plugin.
I also have Java v.8 update 45 (1.8.0_45-b14) installed more traditionally, but one might be messing with the other.
Before the IntelliJ 14 update, I didn't have a problem running 64bit with this setup, but after the update it was a no-go.
It looks like Eclipse might be compatible with later versions of Java now, so when I get a chance (oh, god, in like three months) I'll try cleaning up my environment and see if that does the trick.
-
repo owner Okay. You can choose a specific JRE for use with IntelliJ IDEA:
That will let you use one for Eclipse and another for IntelliJ. I run under 1.8.0_11 and have not seen the issue you're seeing loading IC under a 64-bit host JRE.
-
Bingo! Installed the 1.8 JDK, repointed my JAVA_HOME environment variable, and I'm up and running with IntelliJ 64bit.
Eclipse appears to be coping, too.
Thank you so much! You can close this ticket.
-
repo owner - changed status to resolved
-
repo owner - removed component
Removing component: IntelliJ IDEA (automated comment)
- Log in to comment
Thanks for forwarding this, Maxim. I'll follow up on you guys' tracker as well, but any additional information about the host environment? I and many other users use this plugin in IntelliJ IDEA 64-bit (idea64.exe) with no issues, so there must be something distinct about this user's environment contributing to this startup failure.