JVM crash

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0xa) at pc=0x000000010a8160d0, pid=33423, tid=22531
#
# JRE version: 7.0_25-b15
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C  [libzip.dylib+0x30d0]  newEntry+0x154
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# ...com.lopexs.arl.content.ui.test/hs_err_pid33423.log
#
# If you would like to submit a bug report, please visit:
#  http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Looks like not a JVM bug but a zip library bug, right?

Did you already turn on the core dumps using ulimit -c unlimited and see what it gives?

gdb `which java` core
bt

That will give you a stack trace into the C code and a hint of what might be going wrong. Also, I would read hs_err_pid33423.log

Yes it looks like a bug in the standard zip library.

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J  java.util.zip.ZipFile.getEntry(J[BZ)J
J  java.util.zip.ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry;
j  org.apache.felix.framework.util.WeakZipFileFactory$WeakZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry;+11

We have a quite simple test that reproduces the problem now, and will submit that as a jdk bug.

@paulbakker, could you provide the link to the bug ticket you created for this?

I got the same question: Did you file a ticket with Oracle? Did they resolve it?

I'm hitting this issue as well - @paulbakker - did you open a bug?