JDK-6652168 : sun/java2d/OpenGL/DrawBufImgOp.java crashes in the libmlib_image
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_suse_sles_10
  • CPU: x86
  • Submitted: 2008-01-18
  • Updated: 2011-01-19
  • Resolved: 2008-01-21
Related Reports
Duplicate :  
JDK-6501871 - java.awt.LookupOp may crash on BufferedImage with alpha
Relates :  
JDK-4886506 - VM crashes when using RescaleOp with certain buffered image types
Description
JDK		    : Fails:  6u10
                      Passes: 7 b08

Platform Tested     : Suse 10
		      
Failing Test [s]    : sun/java2d/OpenGL/DrawBufImgOp.java


    Test output:
    ============
----------System.out:(21/808)----------
Could not enable OpenGL pipeline for default config on screen 0
type=1 size=32
type=1 size=17
type=2 size=32
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x4ae5d8a6, pid=27967, tid=1255742384
#
# Java VM: Java HotSpot(TM) Client VM (11.0-b09 mixed mode linux-x86)
# Problematic frame:
# C  [libmlib_image.so+0x5b8a6]
#
# An error report file with more information is saved as:
# /net/sqenfs-2/export2/results/regression/6u10/b10/regression-reg-6u10-suse10-2008-01-15-15-24-49-0726/rerun/work/scratch/hs_err_pid27967.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.
#
----------System.err:(0/0)----------
result: Failed. Unexpected exit from test [exit code: 134]
Comments
EVALUATION First, I would like to note that failure was observed when OpenGL was not initialized due to graphics misconfiguration. It is not regression per se because it can be reproduced with earlier releases. Therefore, I'll remove regression keyword. The crash itself is bug in the medialib-based imaging ops and it is known one. See 6501871 and 4886506 that were fixed in jdk 7. Technically, to resolve this problem in 6u10 we can consider the backport of fixes for 6501871 and 4886506. Please open SubCRs if backport is required.
21-01-2008