Page 1 of 1

Error on Chrome with 5.1.1

Posted: Mon Aug 04, 2014 2:57 pm
by swmatisa
Win7 SP1 64 bits
Ranorex 5.1.1
Chrome Version 36.0.1985.125 m

*********************************
Hello,
I update to version 5.1.1 from 5.1.0 and I receive the following message in the "status" windows:
RanorexErrorMsg.png
The program continue and Ranorex give no other error or warning (in the report).

The snapshot:
Win7ChromeException.rxsnp
Regards

Re: Error on Chrome with 5.1.1

Posted: Wed Aug 06, 2014 12:32 pm
by Support Team
Hi swmatisa,

Thank you for reporting the issue. It seem that the tab in Google Chrome was closed during the test and the WebDocument is still in use.
Can you please check if this is the case?

Regards,
Bernhard

Re: Error on Chrome with 5.1.1

Posted: Thu Aug 07, 2014 8:28 am
by swmatisa
Hello,

I directly send to you my project.

Re: Error on Chrome with 5.1.1

Posted: Fri Aug 08, 2014 2:26 pm
by Support Team
Hello,

Thanks for the sample!
We will analyze it and get back to you as soon as possible!

Regards,
Markus

Re: Error on Chrome with 5.1.1

Posted: Tue Aug 12, 2014 12:16 pm
by Support Team
Hello swmatisa,

Thank you for providing the requested project. Unfortunately, we were not able to reproduce the issue on our side. Usually, a LineageGlueRule exception is thrown if a tab is closed while searching for an element within this tab. I’m afraid that we cannot change this behavior since it’s related to Chrome and not to Ranorex itself.

Regards,
Robert

Re: Error on Chrome with 5.1.1

Posted: Wed Aug 13, 2014 10:36 am
by swmatisa
Hello,
Support Team wrote:Usually, a LineageGlueRule exception is thrown if a tab is closed while searching for an element within this tab. I’m afraid that we cannot change this behavior since it’s related to Chrome and not to Ranorex itself.
I close no tab. I didn't change Chrome and It was working with previous version of Ranorex. I must add a delay after the last click (change page). The "load" of the new page is no more treated as before. It is solved for me, but I hope this "beavior" didn't hide another problem.

Thanks