Skip to main content
Super User

Return to Answer

Fixed grammar.
Source Link
MMB
MMB
  • 596
  • 2
  • 7

These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launchlaunched by root.

Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).

There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then

~ ps -e | grep 13924
13924 ??         0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino

I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.

These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launch by root.

Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).

There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then

~ ps -e | grep 13924
13924 ??         0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino

I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.

These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launched by root.

Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).

There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then

~ ps -e | grep 13924
13924 ??         0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino

I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.

Source Link
MMB
MMB
  • 596
  • 2
  • 7

These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launch by root.

Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).

There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then

~ ps -e | grep 13924
13924 ??         0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino

I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.