Bill, This is a good analysis of the problem.
The method IE.new_process was specifically designed to avoid these problems. Personally, however, I wouldn't start and stop a browser for each test. This entails a lot of overhead, and really slows things down. Bret Bill Agee wrote: > I faced a similar problem a long while back - intermittently, when > starting a new browser immediately after closing another, I would get > an OLE exception. > > I never found the root cause, but if I remember correctly, I noticed > that iexplore.exe continued to run for a short time after I called > IE#close. So I tried doing the following, which solved the problem: > > - Start the browser, let its tests run, close the browser > > - Begin a loop that waits for iexplore.exe to exit > > - Don't start the next browser instance until iexplore.exe is gone > > This may not work for you if you need to have more than one browser > running. But for me it was fine since I can only run one window at a > time. :) > > Thanks > Bill > > On Fri, Oct 16, 2009 at 3:23 AM, pallavi shashidhar > <[email protected] <mailto:[email protected]>> wrote: > > Hi There, > We have a couple of watir scripts that are run as regression suite > on a CI server (cruise control). > Have installed Ruby 1.8.6.26 and watir 1.6 with IE7. > System specification ; windows server 2003 edition, 500gb, 4gb RAM > > All the scripts are made independent and hence we have a > start_browser and browser.close at setup and teardown. > After a while, i find that ie keeps hanging and am not able to > proceed unless i close the browser manually and yet i see that the > ie process is not being killed. > This leads us to lot of RPC server unavailable errors: > > When the suite is run again, i get a lot of these errors: > > |failed to create WIN32OLE object from `InternetExplorer.Application' > HRESULT error code:0x80004005 > Unspecified error (WIN32OLERuntimeError) > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:167:in > `initialize' > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:167:in > `new' > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:167:in > `create_browser_window' > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:91:in > `_new_window_init' > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:81:in > `new_window' > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:105:in > `start_window' > c:/ruby/lib/ruby/gems/1.8/gems/watir-1.6.2/lib/watir/ie-class.rb:99:in > `start' > > c:/ruby/lib/ruby/gems/1.8/gems/commonwatir-1.6.2/lib/watir/browser.rb:71:in > `start'| > > Have tried one of the 3 solutions that Bret has mentioned i.e, > Create an additional IE. As long as this lives, the IE server will > continue to live and you can close and create IE windows without > worry. > > Inspite of having done this, i get the errors. We cannot > completely avoid opening and closing of browsers as more and more > scripts are added to the regression suite. > What could be the reason for ie to hang and how can that be avoided? > > Regards, > Pallavi > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to [email protected] Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
