<AWT Dev>  Review request for 7117595: ArrayIndexOutOfBoundsException in Win32GraphicsEnvironment if display is removed
anthony.petrov at oracle.com
Wed Sep 25 03:12:55 PDT 2013
This version of the fix looks fine to me. Thanks.
On 09/25/2013 01:53 PM, sergey malenkov wrote:
> In the following version of the fix I just return null:
> On 24.09.2013 11:58, Anthony Petrov wrote:
>> Hi Sergey,
>> I think that throwing an AWTError is too risky for JDK 8. We might
>> want to implement this early in JDK 9 though.
>> For now, I think returning null is OK. E.g., see
>> CGraphicsEnvironment.getDefaultScreenDevice(). It simply returns null
>> if there's no screen devices found after a second re-initialization
>> attempt. The rest of code (user apps and tests) seem to be happy with
>> this implementation.
>> best regards,
>> On 09/23/2013 09:59 PM, sergey malenkov wrote:
>>> Could you please review the second version of the fix:
>>> I throw AWTError if there are no more screen devices.
>>> On 23.09.2013 16:47, sergey malenkov wrote:
>>>> Could you please review the following fix:
More information about the awt-dev