Hang in AWT.DLL occurs while running JPI 1.3 builds E and later with Java Accessibility Utilities and "Ferret" sample. Observed on all Win32 platforms under MSIE4/5 and Netscape 4.x. Hang was not observed under build D.

Obscure timing and cursor positioning combination seems to cause sun.awt.windows.WComponentPeer.initCursor to hang, which causes applet's AWT event loop thread to hang.

To reproduce:

1. Install JPI 1.3.
2. Install Java Accessibility Utilities 1.3 beta 1 (I got mine from JDC,
   just copied jars to \lib\ext).
3. Enabled 'Ferret' sample (copy attached accessibility.properties to \lib).
4. Run an applet under the JPI (example is attached).
5. Hang occurs as Java Console comes up and displays proxy info.
   (note that it doesn't happen all the time, and depends on the following
    factors, leading me to suspect an obscure timing situation)
6. If the hang doesn't occur, the Ferret window will come up beside the browser
   and on top of the Java Console.

The hang does not occur if the Java Console is not enabled or the cursor is moved away from the browser after it starts. Under MSIE the cursor has to be
on an area outside of the applet, and so may make it harder to reproduce the hang.

Attached are some descriptions of the thread stacks observed in Java and C++.
lynn.monsanto@eng and kathleen.zelony@eng first observed this.