The AWT Component/MFramePeer classes conspire to give double events when the Frame is resized. The causes excessive screen flash when an application starts up.

To read the code, COMPONENT_MOVED and COMPONENT_RESIZED events are generated
from Component.reshape. However, Component.reshape also calls peer.setBounds,
which in itself is reasonable, except that if you follow the code, if you
are resizing a Frame, you end up in MFramePeer.handleResize() or MFramePeer.handleMoved() which themselves post the corresponding event as well.

Thus, you get *two* RESIZE events posted, and each event will cause the
Frame to call invalidate()/validate()/repaint(), because of Window.dispatchEventImpl. Thus the initial resize of the Frame causes it be
be repainted twice.

See also bug 4138972 which causes the Frame to be repainted a THIRD time
because of RESIZE events being generated when a frame is moved.