JDK-6923520 : Setting Nimbus as default L&F on JDK6u18 (u10+) on Solaris i586 makes Swing unusable (JVM crashes)
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6u10,7
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: solaris
  • CPU: x86
  • Submitted: 2010-02-04
  • Updated: 2012-03-22
  • Resolved: 2010-02-09
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
JDK: 6u10 - 6u18
Platform: Solaris i586
This issue is reproducible on 
 
    zenit.russia.sun.com
    SunOS zenit 5.10 Generic_137112-07 i86pc i386 i86pc

Setting Nimbus L&f introduced in JDK6u10 as default L&F leads to JVM crash 
for almost any attempt to use Swing components. 
About a thousand of JCK Swing tests fails. 
Please see #6923313 for more details.

The issue could be reproduced as follows:

public class Test {
    public static void main(String[] args) {
	new javax.swing.JPanel();
        System.out.println("OK.");
    }
}

The program above if executed with 

 -Dswing.defaultlaf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel

on JDK6u10 - JDK6u18

will lead to 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb5ca4181, pid=28234, tid=2
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) Server VM (16.0-b13 mixed mode solaris-x86 )
# Problematic frame:
# C  [libfontconfig.so.1+0x24181]
#
# An error report file with more information is saved as:
# /home/db158260/temp/nimbus/hs_err_pid28234.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Comments
EVALUATION This issue with zenit.russia.sun.com has been resolved by ###@###.### with the following command (logged in as root): $ /usr/bin/fc-cache --system-only --verbose
09-02-2010

EVALUATION zenit.russia.sun.com is being investigated...
09-02-2010

EVALUATION My suspicion is that this is a platform problem, perhaps due to there being corrupted font caches on the system and/or a bug in the native library. A small C program which uses the /usr/lib/libfontconfig library works fine everywhere but on this system. Also even some apps included with the O/S fail to start, apparently dying due to SEGV in this library. gnome-character-map is a good example. It could be related to Solaris bug 6578750 which is fixed in S10 U6. Note that the JDK6u18 crashes are being reproduced on S10 U5 which therefore lacks that fix.
08-02-2010