Java Plugin is leaving orphaned browser processes open after the browser
has been closed. The problem reproduces with the SwingSetApplet after
the SwingSetApplet.html file has been modified to use Java Plugin.
To reproduce the problem open a webbrowser and load the a SwingSetApplet.html
file that has been modified to use Java Plugin 1.2. After the applet loads completely, close the browser. You will notice that a browser process is still listed in the processes list within the Task Manager. You may have to repeat this process several times. The problem reproduces about 1 out of 5 times. This behavior does not seem to occur when browsing websites or applets that do not use Java Plugin.
I have attached a version of the SwingSetApplet that has been modified to
use Java Plugin. I have reproduced the problem with MS IE4.0. My customer
has reproduced the problem with Netscape 4.06, 4.5, IE 4.0 and IE 5.) on both NT4.0 SP 4 AND NT4.0 SP 3.
has been closed. The problem reproduces with the SwingSetApplet after
the SwingSetApplet.html file has been modified to use Java Plugin.
To reproduce the problem open a webbrowser and load the a SwingSetApplet.html
file that has been modified to use Java Plugin 1.2. After the applet loads completely, close the browser. You will notice that a browser process is still listed in the processes list within the Task Manager. You may have to repeat this process several times. The problem reproduces about 1 out of 5 times. This behavior does not seem to occur when browsing websites or applets that do not use Java Plugin.
I have attached a version of the SwingSetApplet that has been modified to
use Java Plugin. I have reproduced the problem with MS IE4.0. My customer
has reproduced the problem with Netscape 4.06, 4.5, IE 4.0 and IE 5.) on both NT4.0 SP 4 AND NT4.0 SP 3.