Java Issues in macOS Sierra – Running Netbeans or Eclipse Effectively

I use Eclipse (64 Bits) latest Indigo version on Lion and I don't have those crashes.

Your Crashlog comes from a Exception Type: EXC_BAD_ACCESS (SIGSEGV) which is usually:

• A bug in the code (failure to release/retain/etc.) when coding in obj-c (very common).

• A Memory problem (RAM) (hardware).

Given that Eclipse is written in Java (which has Garbage Collection and therefore doesn't suffer from EXC_BAD_ACCESS, as far as I know), I'd say you check your RAM, you might be having a hardware problem that manifests when "memory intensive" (to put it nicely) programs execute.

The dialog is shown because Oracle's Java has only partial 'JVMCapabilities' set and advertises itself as command-line-only capable.

As a superuser (use 'sudo' if editing in Terminal), you should edit /Library/Java/JavaVirtualMachines/jdk.1.7.[version-and-release].jdk/Contents/Info.plist and find the following key:

<key>JVMCapabilities</key>
  <array>
    <string>CommandLine</string>
  </array>

and add it to include the missing values:

<key>JVMCapabilities</key>
  <array>
    <string>CommandLine</string>
    <string>JNI</string>
    <string>BundledApp</string>
  </array>

After that, you have to either reboot, logout or killall Finder, what ever seems to work. (People have reported that restarting Finder was enough, but I had to log out.)

--
Source.