-
Bug
-
Resolution: Cannot Reproduce
-
P2
-
7
-
x86
-
linux_redhat_5.0
Bug Info:
==========
JVM crashes while testing JTextArea component on RHEL5.
JDK Info:
==========
jjava version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b50)
Java HotSpot(TM) Client VM (build 15.0-b02, mixed mode)
Steps to Reproduce:
====================
1. Download the attached code.
2. Run the Application with jdk7-b50.
3. Change the look and feel to GTK.
Expected : The Application should change to GTK look and feel.
Actual : JVM crashes and generates the code dump file.
Error Details:
===============
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb4d5a485, pid=11830, tid=3032300432
#
# JRE version: 7.0-b50
# Java VM: Java HotSpot(TM) Client VM (15.0-b02 mixed mode, sharing linux-x86 )
# Problematic frame:
# C [libfontmanager.so+0xe485]
#
# 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.
#
==========
JVM crashes while testing JTextArea component on RHEL5.
JDK Info:
==========
jjava version "1.7.0-ea"
Java(TM) SE Runtime Environment (build 1.7.0-ea-b50)
Java HotSpot(TM) Client VM (build 15.0-b02, mixed mode)
Steps to Reproduce:
====================
1. Download the attached code.
2. Run the Application with jdk7-b50.
3. Change the look and feel to GTK.
Expected : The Application should change to GTK look and feel.
Actual : JVM crashes and generates the code dump file.
Error Details:
===============
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb4d5a485, pid=11830, tid=3032300432
#
# JRE version: 7.0-b50
# Java VM: Java HotSpot(TM) Client VM (15.0-b02 mixed mode, sharing linux-x86 )
# Problematic frame:
# C [libfontmanager.so+0xe485]
#
# 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.
#