Ranorex Forum

Ranorex 6.0.2
Windows 8.1 Pro on VMWare Enterprise Server

With a new project in an existing solution, when I try to close a DOM object in Chrome on a VM at the end of a test case, Ranorex is throwing an exception. This does not happen on projects that existed prior to the upgrade to 6.0.2, so I'm not sure what the issue is.

It's just a standard Close action on the site's DOM object.

Action 'close' failed on element '{WebDocument:Chrome}'.
Failed to read from an IPC Port: The pipe has been ended.

at Ranorex.Core.Element.InvokeAction(String name, Object[] args)
at Ranorex.Host.CloseApplication(Element containedElement, Duration gracePeriod)
at <Redacted>.<Redacted>.Close_Browser.Ranorex.Core.Testing.ITestModule.Run() in <Redacted>\Close_Browser.cs:line 93
at Ranorex.Core.Testing.TestModuleLeaf.RunInternal(DataContext parentDataContext)


Edit to add: This works on my local Windows 10 Pro system with Ranorex 6.0.2.

Hi Krstcs,

Unfortunately, I'm not able to reproduce your issue on my environment. May I ask you if you could send me a small sample solution where the error occurs?

Thank you in advance.

Sincerely,
Matthias

I forgot to mention that the test is being run by Jenkins through a Jenkins slave running in the logged-in user's context. I don't believe this is an issue though because I have other tests that test a different SUT running in Chrome on Win 7, through Jenkins, and they work just fine.

As for the sample solution, I cannot duplicate the issue with a different, generic solution either. And, unfortunately I can't release the solution that is failing because it is for a third-party partner site and is internal to our domain.

Also, the issue seems to now be limited to Win 8.1 Pro and is intermittent there. I tried the test on one of my Win 7 VMs and it worked, but I haven't done an exhaustive regression test of it yet.

Spoke too soon. It is now also happening on my Windows 7 VMs.

Hi krstcs,

Thank you very much for reporting this issue.
Unfortunately, we are still not able to reproduce this issue on our environment.

It seems to be a timing issue, but it's very hard to analyze this further, since we can't reproduce it.
As a workaround, I would suggest using the form element of the chrome.

We will add this issue to our bug tracking system that we are aware of it, if somebody faces this issue too.

Thank you for your understanding.

Best regards,
Matthias

Matthias,

Thank you for the update.

Friday I set the grace period to 5 seconds and now I'm not seeing the error. Previously it was set to 0 (zero) seconds. My guess is that you are right, that it is a timing issue and that it only happens when the grace period is set too low, but that's just a guess.

Thanks again!

Hi krstcs,

Thank you for your feedback.
I'm glad that your issue could get resolved.

Best regards,
Matthias