Plugin 1.3.1 sometimes runs under explorer.exe rather than iexplore.exe

Question

Mates,
I've written a large application that can also run as a signed applet using the 1.3.1 plugin. It runs beautifully and I'm very happy with the plugin technology. However, I've noticed that for certain users the plugin runs under the shell executable, explorer.exe, instead of the browser executable, iexplore.exe, even though it's started from the browser. When the applet/application is exited, it calls System.exit(0) (not ideal, I know) thereby shutting down the JVM, the plugin, and the executable the plugin is running under. No doubt you can imagine the shock on a user's face when closing my applet caused the shell to crash! This, of course, is happening because Microsoft tried to blur the lines between the browser and the desktop early in the browser wars. I can't figure out how to turn it off!
Can any of you help with this problem. If you'd like to test it, just run a small applet through explorer.exe by right-clicking on "My Computer", Open, navigate to the applet, etc. It helps if you have qslice from the resource kit open so you can see the threads opening under explorer.exe (or iexplore.exe if you try it from a browser). My system specifics are Windows 2000 sp1 with IE 5.
Thanks,
Ziad
[email protected]

Answer 1

Hi Ziad,
Just wondering if you ever found a solution to this problem?
I am experiencing a similar situation where browser windows are controlled by the same Explorer.exe process (not IExplore.exe) on certain machines. This means that when the browser windows are closed and reopened, the JVM is not reset. Because the machines are up for long periods of time, the JVM eventually runs out of memory and crashes.
I am trying to find a way of forcing browser windows to be spawned in separate IExplore.exe processes (instead of running under Explorer.exe).
Help Appreciated,
Mark