Bug ID: JDK-6226054 Dialogue doesn't appear when a new window is invoked at the same time in 1.4.2

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other	JDK 6
5.0u10Resolved	6u1Resolved

The attached applet program shows 2 buttons and textfield.
One button invokes a nw window and another does a dialogue.
We can specify sleep time until new widnows shows up in textfield.

PROBLEM :
 When we click "new Window" button and then "call dialog" button,
 dialog does not appear in some cases.

HOW TO REPRODUCE :
  1) specify the sleep time value from 0 to about 250 in the textfield.
  2) click "new Window" button and then "call dialog" button
  3) you can not find out any dialogue which should have appeared.

NOTE :
  If we specify larger value than 260[ms] in the text field, the dialogue
  will show up at the background of new window.

CONFIGURATION :
  JRE : 1.4.2_06/5.0fcs
  OS  : WindowsXP (Japanese, SP1)
  MPU : Pentium IV 1.4[GHz]
  MEM : 384[MB]



###@###.### 2005-2-07 07:08:19 GMT

EVALUATION Since we have now responce on this issue for a ong time, I'm closing the bug as not reproducible. Feel free to reopen it with moe information.
24-10-2006
EVALUATION I can't reproduce the described defect with JRE6.0RC. Instead I'm experiencing that a newly appeared window become "zombie": it's not accessible and not visible on the screen but it presented in a taskbar and in TaskManager's list. Moreover, first window is still responsible but new window is not appearing anymore. Perhaps it's specific to JDK6.0. I'm attaching a stack dump but it looks okay. According to screenshot this is another problem then submitter experiencing as he seem to be able to operate with that new window. Seem I've to try JRE5.0 also.
30-08-2006
EVALUATION I suspect it's windows os that doesn't deliver WM_LBUTTONDOWN to java button. we can check that by examine whether the window procedure of native peer of java button receives mouse event. so transfer to awt for checking that.
25-08-2006
EVALUATION we need to figure out whether windows OS swallows the message
24-08-2006
EVALUATION I doubt the mouse event is dispatched to the new window by windows. When I test the testcase, sometime I can reproduce this bug. but after I move the original window to a place so that the button in it is not covered by the new window, the dialog always pop up, or at least I cannot reproduce this bug in this case. So please test again after moving window. I also create two buttons using pure javascript, it seems same issue can happen.
18-07-2006
EVALUATION I still have not been able to isolate where this race condition is happening. I do know for sure that the JavaScript call "window.open" is somehow interfering with the Java event thread.
26-10-2005
EVALUATION After doing a code trace, the problem is not so much that a dialog does not come up, but the "actionPerformed" method which brings up the dialog does not even get called. Therefore, this is not a dialog issue, but an events issue. The problem has been traced down to plug-in making a javascript call. There is a Windows API call "SetEvent" which gets called in the "DispatchWrapper.cpp" file. It's my theory that there is something going on with the Windows level event with regards to it being signaled. It appears that this call may be blocking the other event thread from going thru ... or consuming it, which is why the event to launch the dialog never gets thru.
26-08-2005

Relates :	JDK-4791917 - VM and Netscape both freese when new applet window and modal dialog comes up.
Relates :	JDK-6418035 - Applets freeze in 5u7 on XP Japanese