On win32, it is necessary to send the display change event to all heaveyweight
components and offscreen images, to make sure that any display-dependent
data they have (such as the internal surface data objects) are updated with
the new display information.

In the latest 1.4 code, the display change is not being propagated
correctly and ends up missing some embedded heavyweight components.

For example, an application that embeds a heaveyweight component
(for example, a Canvas) in the contentPane of a JFrame will not
be updated properly.

This problem can have indeterminate side effects, such as screen garbage
or application crashes due to bad memory references.