<AWT Dev> [8] Review request for 7117595: ArrayIndexOutOfBoundsException in Win32GraphicsEnvironment if display is removed

Anthony Petrov anthony.petrov at oracle.com
Tue Sep 24 00:58:28 PDT 2013

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:
> http://cr.openjdk.java.net/~malenkov/7117595.8.1/
> I throw AWTError if there are no more screen devices.
> On 23.09.2013 16:47, sergey malenkov wrote:
>> Hello,
>> Could you please review the following fix:
>> fix:http://cr.openjdk.java.net/~malenkov/7117595.8.0/
>> bug:https://bugs.openjdk.java.net/browse/JDK-7117595
>> Thanks,
>> SAM

More information about the awt-dev mailing list