JDK-8147077 : IllegalArgumentException thrown by api/java_awt/Component/FlipBufferStrategy/indexTGF_General
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux,solaris
  • Submitted: 2016-01-14
  • Updated: 2017-01-11
  • Resolved: 2016-01-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 JDK 8 JDK 9 Other
7u121Fixed 8u111Fixed 9 b107Fixed openjdk7uFixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Testsuite name: JCK runtime 
TestSuite Version : jck-runtime-9/b27 
Test Name(s):api/java_awt/Component/FlipBufferStrategy/indexTGF.html\#General
Product(s) tested: JDK 9 b100(64bit) 

Reproducible: Always 

Is it a Regression: Yes 
[If regression]Issue was introduced in JDK9b100 

Is it a platform specific issue: Yes 
[If platform specific issue] It fails with Solaris 11 sun4u, Solaris 12 x64, Linux x64.
Comments
URSQE OK to take the tck-red regression bug fix to CPU16_04
08-08-2016

Could you please push the fix to 8u-CPU. We would like to run nightly for the fix.
03-08-2016

Is it possible to get a standalone testcase showing the problem as I do not have a JCK setup. Also, I will like to know if this jck test fails on windows. This is because IAE was thrown on windows if VolatileImage of 0 width and height was asked to be created even before JDK-8140530 fix. JDK-8140530 just cause IAE to be thrown for VolatileImage of 0 width,height on linux platform just to make it consistent with windows behaviour and also with createCompatibleImage(0,0) or a BufferedImage(0,0,imagetype) where it was already resulting in IAE. So, is the JCK test expects IAE on windows and not on linux? why that will be the case?
21-01-2016

RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" Exception java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingCanvas] test cases: 4; all failed; first test case failure: constructor_enclosingCanvas RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingCanvas_lessThanTwoBuffers_IAE] test cases: 4; all failed; first test case failure: constructor_enclosingCanvas_lessThanTwoBuffers_IAE RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingCanvas_noPageFlipping_IAE] test cases: 4; all failed; first test case failure: constructor_enclosingCanvas_noPageFlipping_IAE RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingCanvas_nopeer_ISE] test cases: 4; all failed; first test case failure: constructor_enclosingCanvas_nopeer_ISE RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingWindow] test cases: 4; all failed; first test case failure: constructor_enclosingWindow RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingWindow_lessThanTwoBuffers_IAE] test cases: 4; all failed; first test case failure: constructor_enclosingWindow_lessThanTwoBuffers_IAE RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingWindow_noPageFlipping_IAE] test cases: 4; all failed; first test case failure: constructor_enclosingWindow_noPageFlipping_IAE RULE "api/java_awt/Component/FlipBufferStrategy/indexTGF_General" TestCase [constructor_enclosingWindow_nopeer_ISE] test cases: 4; all failed; first test case failure: constructor_enclosingWindow_nopeer_ISE
19-01-2016

regression of JDK-8140530
18-01-2016