Details
-
Bug
-
Resolution: Fixed
-
P4
-
17, 18
-
None
-
b13
-
x86_64
-
windows
Description
A DESCRIPTION OF THE PROBLEM :
On Windows platform, default drawing pipeline (D3D) processes multiple PaintEvent at initial drawing. This behavior does not occur on GDI pipeline (-Dsun.java2d.noddraw=true).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
compile and run attached sample code on Windows platform. This sample counts a number of paint() calls.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Green window is shown and "1" is printed on console.
ACTUAL -
Red window is shown and print "2" is printed on console.
This additional PaintEvent is unnecessary and may cause performance issue.
On Windows platform, default drawing pipeline (D3D) processes multiple PaintEvent at initial drawing. This behavior does not occur on GDI pipeline (-Dsun.java2d.noddraw=true).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
compile and run attached sample code on Windows platform. This sample counts a number of paint() calls.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Green window is shown and "1" is printed on console.
ACTUAL -
Red window is shown and print "2" is printed on console.
This additional PaintEvent is unnecessary and may cause performance issue.
Attachments
Issue Links
- is cloned by
-
JDK-8299436 [REDO] D3D pipeline processes multiple PaintEvent at initial drawing
- Open
- relates to
-
JDK-8282713 Invalid copyright notice in new test added by JDK-8275715
- Resolved
-
JDK-8298876 Swing applications do not get repainted coming out of sleep on Windows 10
- Resolved