JDK-6553958 : JVM crash when running NetBeans 6.0
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_10
  • CPU: sparc
  • Submitted: 2007-05-04
  • Updated: 2010-05-09
  • Resolved: 2007-07-12
Related Reports
Duplicate :  
JDK-4425695 - Updating jar files crashes running programs
Description
I was running NetBeans 6.0 (daily build circa 5/4/07) on JDK 1.6.0_00 (FCS) on my Ultra20M2 (Solaris 10, 11/06 express build) and the JVM crashed unexpectedly.

#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGBUS (0xa) at pc=0xfeeb46ce, pid=7392, tid=342
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing)
# Problematic frame:
# C  [libc.so.1+0x246ce]  memcpy+0x15e
#
# An error report file with more information is saved as hs_err_pid7392.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
7392 Abort
Comments
EVALUATION The additional information in the Comments suggests that this is another instance of aJAR file getting changed while being already open by the JVM.
12-07-2007
EVALUATION Wishful thinking perhaps, but: is the crash reproducible? We have seen instances in the past where the JVM has a jar file opened, and another entity (process, etc) changes that same jar file: subsequent attempts at accessing the open jar file cause JVM crashes. See 6390352, 4425695. Do you have any reason to believe that any JVM-opened jar files are being changed behind the scenes?
18-05-2007