JDK-6979882 : api/java_awt/Font/TextLayout/indexTGF.html#EqHashCodeStandard crash open solaris x64 32bit jdk
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: open_solaris
  • CPU: x86
  • Submitted: 2010-08-25
  • Updated: 2012-03-22
  • Resolved: 2010-10-27
Related Reports
Duplicate :  
Description
platform-specific regression.
api/java_awt/Font/TextLayout/indexTGF.html#EqHashCodeStandard crashes on OpenSolaris 2009.06 x64 using 32-bit JDK. currently it is confirmed it just normally fails on Windows, OpenSolaris sparc, Linux, Solaris 10 systems.

[stt-robot@stt-38]$ /export/jdk/jdk1.7.0/bin/java -showversion -Xfuture -classpath /export/JCK/JCK-runtime-7/classes:/export/jdk/jdk1.7.0/lib/tools.jar -Djava.security.policy=/export/JCK/JCK-runtime-7/lib/jck.policy javasoft.sqe.tests.api.java.awt.Font.TextLayout.EqHashCodeStandard
java version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b106)
Java HotSpot(TM) Client VM (build 19.0-b05, mixed mode, sharing)

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xfe5aabad, pid=28997, tid=2
#
# JRE version: 7.0
# Java VM: Java HotSpot(TM) Client VM (19.0-b05 mixed mode, sharing solaris-x86 )
# Problematic frame:
# V  [libjvm.so+0x1aabad]
#
# An error report file with more information is saved as:
# /net/vice/export/stt/newroot/net_homes/stt-38/hs_err_pid28997.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Abort (core dumped)

Comments
EVALUATION The crash happens when method getPlatformFontPathChars() tries to get awt lock (fontpath.c, line 505) by a call for AWT_LOCK(). AWT_LOCK() performs an upcall to java, which is listed in the crash dump: V [libjvm.so+0x1aabad] CallStaticVoidMethod(env, tkClass, awtLockMID) C [libmawt.so+0x1f69e] getPlatformFontPathChars C [libmawt.so+0x1f794] Java_sun_awt_X11FontManager_getFontPath+0x30 So, this looks like an AWT problem.
26-10-2010