<AWT Dev> update on JDK-8046290 (garbage pixels on OS X)

Alan Snyder javalists at cbfiddle.com
Sun Nov 29 19:39:12 UTC 2015


I believe I have encountered this previously reported bug and understand the cause. It is a timing problem that occurs when native code asks for pixels (
drawInCGLContext) at the same time that LWWindowPeer is trying to replace the surface data. The problem occurs if the request for pixels happens after a new CGLSurfaceData has been created but before it is initialized with a background color. In most cases, this error results in a transient flicker, but if the window is transparent, then the garbage pixels will be painted over by the background color and remain visible. Unfortunately, I have code that frequently runs into this problem.

I have attached a test case that is reliable (for me) on 1.8.0_66.

I hope with this new information the bug will be fixed soon.

  Alan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: Test.java
Type: application/octet-stream
Size: 904 bytes
Desc: not available
URL: <http://mail.openjdk.java.net/pipermail/awt-dev/attachments/20151129/3f2e193c/Test-0001.java>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Uninitialized Pixels Screen Shot.png
Type: image/png
Size: 461398 bytes
Desc: not available
URL: <http://mail.openjdk.java.net/pipermail/awt-dev/attachments/20151129/3f2e193c/UninitializedPixelsScreenShot-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Uninitialized Pixels Screen Shot 2.png
Type: image/png
Size: 358029 bytes
Desc: not available
URL: <http://mail.openjdk.java.net/pipermail/awt-dev/attachments/20151129/3f2e193c/UninitializedPixelsScreenShot2-0001.png>


More information about the awt-dev mailing list