United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6927268 ShowDocument calls results in new iexplorer process
JDK-6927268 : ShowDocument calls results in new iexplorer process

Details
Type:
Bug
Submit Date:
2010-02-17
Status:
Resolved
Updated Date:
2012-10-01
Project Name:
JDK
Resolved Date:
2010-05-04
Component:
deploy
OS:
windows_xp
Sub-Component:
plugin
CPU:
x86,generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6u18
Fixed Versions:
6u20-rev (b05)

Related Reports
Backport:
Backport:
Backport:
Duplicate:
Duplicate:
Duplicate:
Relates:
Relates:

Sub Tasks

Description
Customer upgraded from 6.0_17 -> 6.0_18


Steps to reproduce

1.  Windows XP SP 3 with IE6.  Discovered that IE8 always spawns a new process for iexplore.exe
2.  Install jdk 6u17
3.  Test by opening the applet with IE6
4.  Click in url field and hit return
5.  IE6 browser window is opened.  Check task manager and no extra iexplore.exe spawned
6.  Install jdk 6u18
7.  Repeat the test and you will see that there are 2 iexplore.exe processes this time.

                                    

Comments
EVALUATION

Using the spy++ tool to monitor activation and focus related messages on the JFrame. 
When the bug is reproduced:
===========================
clicking on the applet's "Go!" button
-------------------------------------
<00001> 0014065A S WM_PARENTNOTIFY fwEvent:WM_LBUTTONDOWN xPos:246 yPos:18
<00002> 0014065A R WM_PARENTNOTIFY
<00003> 0014065A S WM_MOUSEACTIVATE hwndTopLevel:0014065A nHittest:HTCLIENT uMsg:WM_LBUTTONDOWN
<00004> 0014065A R WM_MOUSEACTIVATE fuActivate:MA_ACTIVATE
<00005> 0014065A S WM_ACTIVATEAPP fActive:True dwThreadID:00000000
<00006> 0014065A R WM_ACTIVATEAPP
<00007> 0014065A S WM_ACTIVATE fActive:WA_CLICKACTIVE fMinimized:False hwndPrevious:(null)
<00008> 0014065A R WM_ACTIVATE

below shows after closing the new browser window
-------------------------------------------------
<00009> 0014065A S WM_ACTIVATE fActive:WA_INACTIVE fMinimized:False hwndPrevious:(null)
<00010> 0014065A R WM_ACTIVATE
<00011> 0014065A S WM_ACTIVATEAPP fActive:False dwThreadID:000014D4
<00012> 0014065A R WM_ACTIVATEAPP
<00013> 0014065A S WM_ACTIVATEAPP fActive:True dwThreadID:000014D4
<00014> 0014065A R WM_ACTIVATEAPP
<00015> 0014065A S WM_ACTIVATE fActive:WA_ACTIVE fMinimized:False hwndPrevious:(null)
<00016> 0014065A R WM_ACTIVATE
<00017> 0014065A S WM_ACTIVATE fActive:WA_INACTIVE fMinimized:False hwndPrevious:(null)
<00018> 0014065A R WM_ACTIVATE
<00019> 0014065A S WM_ACTIVATEAPP fActive:False dwThreadID:000010A8
<00020> 0014065A R WM_ACTIVATEAPP

When the bug isn't reproduced - using old plugin:
=================================
left click on the applet's "Go!" button
----------------------------------------
<00001> 00160614 S WM_PARENTNOTIFY fwEvent:WM_LBUTTONDOWN xPos:254 yPos:16
<00002> 00160614 R WM_PARENTNOTIFY
<00003> 00160614 S WM_MOUSEACTIVATE hwndTopLevel:00160614 nHittest:HTCLIENT uMsg:WM_LBUTTONDOWN
<00004> 00160614 R WM_MOUSEACTIVATE fuActivate:MA_ACTIVATE
<00005> 00160614 S WM_ACTIVATEAPP fActive:True dwThreadID:00000000
<00006> 00160614 R WM_ACTIVATEAPP
<00007> 00160614 S WM_ACTIVATE fActive:WA_CLICKACTIVE fMinimized:False hwndPrevious:(null)
<00008> 00160614 R WM_ACTIVATE

the following appears right away upon the new browser window shown
------------------------------------------------------------------
<00009> 00160614 S WM_ACTIVATE fActive:WA_INACTIVE fMinimized:False hwndPrevious:(null)
<00010> 00160614 R WM_ACTIVATE
<00011> 00160614 S WM_ACTIVATEAPP fActive:False dwThreadID:00001574
<00012> 00160614 R WM_ACTIVATEAPP

When the problem happened, the WM_INACTIVE never got delievered to the JFrame in time; it was delievered after the new browser window was closed.
                                     
2010-04-01



Hardware and Software, Engineered to Work Together