Phlip wrote: > Bret Pettichord wrote: > > >> (I plan to commit this to Watir, but since you asked, i'm sending it >> direct. Using this you do ie = IE.new_process to create an IE and >> ie.kill to close it. This creates a separate IE process for each Window >> > > If my current system turns ruby.exe off at the end of a test batch, > shouldn't that take down all the zombie IE Automation objects it > spawned? And their handles? > >
I don't know. I don't know if it should and i don't know if it does. You can check to see if there is an IEXPLORE.exe process running when you are done. My experiments have shown that 30 seconds after the ruby script completes, the IEXPLORE.exe process will stop. But this seems to be different from what happens for other people. We've often had reports of problems when suites repeatedly open and close IE windows. I mostly avoid it, and wrote the code i sent you because i had a case where i couldn't, and i wanted to manage IE at the process level, rather the OLE way that Watir has traditionally used, and which seems to lead to a lot of trouble. Bret _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
