-
Bug
-
Resolution: Unresolved
-
P4
-
17, 18
-
x86_64
-
windows
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.
The fix for this issue caused some regression likeJDK-8298876 and also the regression test provided fails in some CI systems and is problem listed which suggests the fix was half-baked and there are some corner cases which are not tested.
So the fix is going to be reverted and will be fixed properly under this id.
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.
The fix for this issue caused some regression like
So the fix is going to be reverted and will be fixed properly under this id.
- clones
-
JDK-8275715 D3D pipeline processes multiple PaintEvent at initial drawing
- Resolved
- relates to
-
JDK-8298876 Swing applications do not get repainted coming out of sleep on Windows 10
- Resolved