EVALUATION

The fix has been integrated as a part of the fix for 6806217.
                                     

EVALUATION

The fix is going to be integrated in jdk7 as a part of the fwd-ported 6693253.
                                     

EVALUATION

As I can see. WM_IME_NOTIFY comes to the proxy at the moment when I click
to the second frame (not the owner). The messages contains wParam equal to
IMN_CLOSESTATUSWINDOW. The component corresponding to the current sm_focusOwner
value is retrived and the message is forwarded to its WindowProc.
The problem is that by this time the sm_focusOwner has already been reset to
the new focused component (in the second frame I had clicked).

To solve the problem we can retain the most recent focused component
proxied by the proxy. And then forward IME messages to it appropriately.
                                     

EVALUATION

Some investigation showed that the crash happens when we call DefWindowProc for a message WM_IME_NOTIFY, from AwtFrame::ProxyWindowProc (~awt_Frame.cpp:331 in my workspace). From the attached HotSpot log file, I roughly see, what's going. When I press the title of the left frame, we call WInputMethod.enableNativeIME(), then send a message WM_AWT_ASSOSIATECONTEXT to the toolkit thread, then call AwtComponent::ImmAssosiateContext() and call the native ::ImmAssosiateContext(). This leads to the message WM_IME_SETCONTEXT which is unhandled and forwarded to DefWindowProc, and then WM_IME_NOTIFY, also forwarder to DefWindowProc.
                                     

EVALUATION

Undoing the changes made in awt_Component.cpp for 6359035 stopped the crashing. 
Reassigning this CR to awt team. 
Thanks.