[OpenJDK 2D-Dev]  Review Request: 8185093 Expensive multi-core choke point when any graphics objects are created
james.graham at oracle.com
Mon Jul 31 20:32:24 UTC 2017
I adjusted one of the statements to be a little more straightforward and set the compatibility risk to minimal. If Phil
thinks the risk can be set to "None", that was my alternate, but I stuck with "minimal" to be safe...
On 7/28/17 5:07 PM, Sergey Bylokhov wrote:
> DRAFT version of CSR:
> ----- philip.race at oracle.com wrote:
>> On 07/24/2017 05:09 PM, Sergey Bylokhov wrote:
>>> The main issue which I would like to clarify is it possible to
>>> synchronize keyword from the getLocalGraphicsEnvironment(), possibly
>>> with updating a specification? We have similar issues in other parts
>>> of code which I would like to update later after this one.
>> Yes, I do think we can remove synchronized but we should do a CSR
>> On 07/25/2017 03:03 PM, Jim Graham wrote:
>>> +1 for the inner class version - it's the most straightforward way
>>> do this optimally...
>> Same from me.
More information about the 2d-dev