This has been given a Java bug number now: JDK-8212124
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8212124
I have been following the discussion here and I have a couple of
workarounds to try, which is great.
But, is there any more information you need from me? I'm always happy to
If there are no comments in the source, then there is no documentation :-(
Reverse engineering/studying the code is what we'd have to do if that were
the approach to be taken here.
-phil.
On 10/12/18, 2:18 AM, Laurent Bourgès wrote:
Phil,
I looked at the hostpot in
Thanks Sergey.
On 10/11/18, 5:43 PM, "Sergey Bylokhov" wrote:
Hi, Bill.
The similar bug was reported recently:
https://bugs.openjdk.java.net/browse/JDK-8211992
The root cause is how we use CoreGraphics display ID. This identifier can
become non-valid at any time
Ping? Since this fix addresses build failure which will affect
production, I guess this needs to go in asap.
Regards
Prasanta
On 11-Oct-18 1:39 PM, Prasanta Sadhukhan wrote:
Hi All,
Please review a build issue fix for usage of
NSPrintJobDispositionValue in JDK-8211055
Hi Prasanta,
Changes are fine.
Thanks,
Jay
From: Prasanta Sadhukhan
Sent: Thursday, October 11, 2018 1:40 PM
To: 2d-dev
Subject: [OpenJDK 2D-Dev] [12] RFR JDK-8212040: Compilation error due to wrong
usage of NSPrintJobDispositionValue in mac10.12
Hi All,
Please review a build
Phil,
I looked at the hostpot in
src/java.desktop/share/native/libawt/java2d/pipe/ShapeSpanIterator.c (75%
cpu time) and its sort algorithm looks like an insertion sort ...
If you could give me some explanations (or documentation), I could try
optimizing this method.
Do you know if it uses an
Excellent. That looks like the same bug. Note that it also affects JDK8.
Bill
On 10/11/18, 5:43 PM, "Sergey Bylokhov" wrote:
Hi, Bill.
The similar bug was reported recently:
https://bugs.openjdk.java.net/browse/JDK-8211992
The root cause is how we use CoreGraphics
