-
Bug
-
Resolution: Fixed
-
P3
-
7u6
The es2n pipeline initialization code crashes on Linux in OpenGL initialization code if DISPLAY env variable is not set (will probably also crash if X server not running).
The following is from a Hudson run with the DISPLAY variable not correctly setup. The expected behavior is that pipeline initialization should fail gracefully, falling back to the j2d software pipeline. Any tests that try to open a Stage will subsequently fail with a Headless exception, but this particular test does not try to do that.
[junit] Testsuite: classloader.ClassLoader1Test
[junit] #
[junit] # A fatal error has been detected by the Java Runtime Environment:
[junit] #
[junit] # SIGSEGV (0xb) at pc=0x77725d43, pid=25798, tid=2004327280
[junit] #
[junit] # JRE version: 6.0_16-b01
[junit] # Java VM: Java HotSpot(TM) Server VM (14.2-b01 mixed mode linux-x86 )
[junit] # Problematic frame:
[junit] # C [libprism-es2n.so+0x5d43] Java_com_sun_prism_es2n_gl_x11_X11GLFactory_nInitialize+0x93
[junit] #
[junit] # An error report file with more information is saved as:
[junit] # /BUILD_AREA/HUDSON/builds2/workspace/2.2-gfx-test-sandbox/label/linux-i586-14/rt-closed/tests/app-lifecycle/ClassLoaderTest/hs_err_pid25798.log
[junit] #
[junit] # If you would like to submit a bug report, please visit:
[junit] # http://java.sun.com/webapps/bugreport/crash.jsp
[junit] # The crash happened outside the Java Virtual Machine in native code.
[junit] # See problematic frame for where to report the bug.
[junit] #
[junit] Testsuite: classloader.ClassLoader1Test
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit]
[junit] Testcase: classloader.ClassLoader1Test:testClassLoader: Caused an ERROR
[junit] Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
[junit] junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
The following is from a Hudson run with the DISPLAY variable not correctly setup. The expected behavior is that pipeline initialization should fail gracefully, falling back to the j2d software pipeline. Any tests that try to open a Stage will subsequently fail with a Headless exception, but this particular test does not try to do that.
[junit] Testsuite: classloader.ClassLoader1Test
[junit] #
[junit] # A fatal error has been detected by the Java Runtime Environment:
[junit] #
[junit] # SIGSEGV (0xb) at pc=0x77725d43, pid=25798, tid=2004327280
[junit] #
[junit] # JRE version: 6.0_16-b01
[junit] # Java VM: Java HotSpot(TM) Server VM (14.2-b01 mixed mode linux-x86 )
[junit] # Problematic frame:
[junit] # C [libprism-es2n.so+0x5d43] Java_com_sun_prism_es2n_gl_x11_X11GLFactory_nInitialize+0x93
[junit] #
[junit] # An error report file with more information is saved as:
[junit] # /BUILD_AREA/HUDSON/builds2/workspace/2.2-gfx-test-sandbox/label/linux-i586-14/rt-closed/tests/app-lifecycle/ClassLoaderTest/hs_err_pid25798.log
[junit] #
[junit] # If you would like to submit a bug report, please visit:
[junit] # http://java.sun.com/webapps/bugreport/crash.jsp
[junit] # The crash happened outside the Java Virtual Machine in native code.
[junit] # See problematic frame for where to report the bug.
[junit] #
[junit] Testsuite: classloader.ClassLoader1Test
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit]
[junit] Testcase: classloader.ClassLoader1Test:testClassLoader: Caused an ERROR
[junit] Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
[junit] junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.