-
Sub-task
-
Resolution: Won't Fix
-
P4
-
internal
-
x86_64
-
os_x
MTLBlitLoops.java
static void IsoBlit(SurfaceData srcData, SurfaceData dstData,
BufferedImage srcImg, BufferedImageOp biop,
Composite comp, Region clip,
AffineTransform xform, int hint,
int sx1, int sy1,
int sx2, int sy2,
double dx1, double dy1,
double dx2, double dy2,
boolean texture)
method has a check
if (rtt && oglDst.isOnScreen()) {
and there is a RQ.FlushNow() call if the check passes.
This conditions currently is being evaluated to true always. This could be attributed to unimplemented stuff or work in progress.
This hogs AWT-EventQueue thread to the extent the applications becomes slow responsive.
My suggestion is to comment out this code till the time we actually need it to implement the specific case that the the current if condition handles.
static void IsoBlit(SurfaceData srcData, SurfaceData dstData,
BufferedImage srcImg, BufferedImageOp biop,
Composite comp, Region clip,
AffineTransform xform, int hint,
int sx1, int sy1,
int sx2, int sy2,
double dx1, double dy1,
double dx2, double dy2,
boolean texture)
method has a check
if (rtt && oglDst.isOnScreen()) {
and there is a RQ.FlushNow() call if the check passes.
This conditions currently is being evaluated to true always. This could be attributed to unimplemented stuff or work in progress.
This hogs AWT-EventQueue thread to the extent the applications becomes slow responsive.
My suggestion is to comment out this code till the time we actually need it to implement the specific case that the the current if condition handles.
- blocks
-
JDK-8225175 Evaluate RenderQueue Vs non-RenderQueue Design architecture for Metal Rendering Pipeline implementation
- Closed
- relates to
-
JDK-8228576 Use setNeedsDisplay to start blitting in Appkit thread in Metal
- Resolved