IE is not closed properly at the end of a test run

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Configure jsTestDriver to run IE (confirmed w/ IE 8)
2. Start task Manager
3. Confirm no iexplore.exe processes are listed
4. Run tests
5. Confirm that iexplore.exe process is listed

What is the expected output? What do you see instead?

I expect that if Explorer was not running when the tests start, it shouldn't be 
running at the end

What version of the product are you using? On what operating system?

JSTD 1.2.2 and 1.3.1 both exhibit this behavior.  Possibly 1.2.1 as well. 
Untested with other versions.

Please provide any additional information below.

Each copy is using 18 meg of RAM.  This memory leak eventually brings our CI 
box to a crawl.  

We worked around this by adding a build step (CI machine only) that invokes 
taskkill /T /F iexplore.exe (windows version of kill -9)

Original issue reported on code.google.com by jdmarsh...@gmail.com on 28 Feb 2011 at 6:54

[GoogleCodeExporter]

Sigh. Blame java, in this case. It doesn't seem to be able to handle windows 
processes well. I'll dig around see there is an alternative.

Original comment by corbinrs...@gmail.com on 1 Mar 2011 at 2:34

[GoogleCodeExporter]

Java process kill doesn't cause grandchildren to exit, alas.  I've run into 
trouble with that one, too.

Original comment by jdmarsh...@gmail.com on 1 Mar 2011 at 11:46

[GoogleCodeExporter]

Hi,

Is there anyone looking into this issue?
I'm facing this issue with a residual IE8 process remaining after tests are run.
Due to the number of tests this IE8 process occupies 1GB of RAM.

I'm at the latest Java update Java 7 Update 25.
Running Win 7 64-bit.

The issue seems over 2 years old, just wanted to get an idea of any fixes that 
are being thought of for this.

Original comment by bap.123p...@gmail.com on 25 Jul 2013 at 7:41