Bug ID: JDK-6662231 FilesInUse Dialog shows OOPP title as "java.exe", should show IE/FF title

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.

JDK 6
6u10Resolved

I tried out the FilesInUse fix, and it looks good for the most part.  I used these builds:

6u10:http://j2se.east/plugin/1.6.0_10-nightly/2008-02-12

6u11:http://j2se.east/plugin/1.6.0_10-nightly/2008-02-12.08_38

The only issue is when I do the following:

1. Install 6u10
2. Open IE
3. View applet with IE at:  http://j2se.east/~billyh/applet.html
4. Now launch 6u11, and it shows 2 entries.  See:

http://j2se.east/~billyh/fiu.JPG

The next generation plugin runs in a different process, therefore that's why the extra java.exe is showing up with the new FilesInUse dialog.  If I switch back to the old plugin, I don't see this issue.  I'm thinking it should only show one item, and not the java.exe.

EVALUATION Here's an email exchange from KenR/Bill: Kenneth Russell wrote: > William Harnois wrote: >> Hmmm. I bet this has to do with new plugin being OOPP. (actually, i just confirmed it). The next generation plugin runs in a different process, therefore that's why the extra java.exe is showing up with the new FilesInUse dialog. If I switch back to the old plugin, I don't see this issue. >> >> I'm not sure what the best approach here is, but we should only be showing the title of the IE window. Maybe there's a way to determine if any java.exe processes are a child process of IE/Firefox, and ignore it in this case. Or Ken, is it possible that the java.exe OOP applet can have it's own Window title? I recall a while back that we'll have the ability to drag applets out of the browser w/out crashing it. > > The windows created by the new plug-in's subordinate java.exe process are in general AWT EmbeddedFrame instances; these basically don't have a window title, though we might be able to forcibly generate one. > > What happens if the Java Console is enabled? I'd guess that the window name "Java Console" will show up in the FIU dialog. This probably isn't desirable either. > > I can think of two ways to detect that a java.exe process is associated with the new Java Plug-In: > > 1. If you're using Process32First / Process32Next for the enumeration of processes, if you encounter a java.exe that doesn't have an associated window title, you can use the th32ParentProcessID and walk up the chain of parent processes. (On Vista, the process chain looks like iexplore.exe -> jp2launcher.exe -> java.exe.) For each parent process, you can use OpenProcess and the ToolHelp APIs to enumerate the DLLs it has loaded, and if it has either jp2iexp.dll or npjp2.dll loaded, then it's a web browser that's loaded the Java Plug-In, and the java.exe is a process associated with the new plug-in. > > 2. You could enumerate the java.exe process's DLLs to see whether it has jp2native.dll loaded. > > There are other possibilities -- you could look for iexplore.exe or firefox.exe as the parent process's names, for example, though I think (1) would be a more robust indicator. (2) is clearly simpler and in the end might be as reliable an indicator. However, you'd still need to walk the parent process tree to get the name of the web browser's window. > > -Ken

12-02-2008

Duplicate :	JDK-6705750 - Need to change logic implementation in FilesInUse for OOPP
Relates :	JDK-6710401 - "FileInUse" dialog have issues with new plugin