Unable to see inside chrome://memory-redirect

Ranorex Spy, Recorder, and Studio.
monsieurmarc
Posts: 2
Joined: Tue Aug 27, 2013 2:39 pm

Unable to see inside chrome://memory-redirect

Post by monsieurmarc » Tue Aug 27, 2013 2:47 pm

Hi,

I have come unstuck trying to parse memory information out of the chrome://memory-redirect page.

I have previously been able to do this with the likes of Watir however the Ranorex Object Spy just cannot see anything inside this page.

Does anyone have a solution to this they could share?

Kind Regards
Marc

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 3930
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Unable to see inside chrome://memory-redirect

Post by odklizec » Tue Aug 27, 2013 3:13 pm

Hi Marc,

As far as I know, Ranorex is not able to recognize the elements on internal Chrome pages. See this post...
http://www.ranorex.com/forum/chrome-can ... tml#p16195
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration

monsieurmarc
Posts: 2
Joined: Tue Aug 27, 2013 2:39 pm

Re: Unable to see inside chrome://memory-redirect

Post by monsieurmarc » Tue Aug 27, 2013 3:15 pm

Thank you I will take a look at the link.

Regards
Marc

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Unable to see inside chrome://memory-redirect

Post by Support Team » Tue Oct 15, 2013 5:31 pm

Hi Marc,

I had a closer look at this very problem and at the Chromium Embedded Framework (CEF) at all.
If Chrome is started with the "--force-renderer-accessibility" parameter, Ranorex is then able to list elements, for example, within the memory-redirect page, as visible in the following figure:
ChromeMemoryTracking.png
ChromeMemoryTracking.png (165.35 KiB) Viewed 105142 times
Unfortunately the tracking of individual elements is currently not possible; however, they are all listed properly in the tree, as visible above and can be properly highlighted. Furthermore, I was able to perform automation tasks on various elements.

Therefore, you just need to start Chrome with the option "--force-renderer-accessibility", for example by adding it to the startup link.
This option might also be useful for other Chromium Embedded Framework applications, as long as they are created with (at least) CEF3.

Kind regards,
Christian
.
Image

User avatar
OverflowingStack
Posts: 8
Joined: Thu Mar 27, 2014 9:35 pm
Location: Clearwater, Florida
Contact:

Re: Unable to see inside chrome://memory-redirect

Post by OverflowingStack » Fri May 23, 2014 2:11 pm

Hello Marc,

I have had success with identifying objects on Chrome internal pages by enabling accessibility at:

chrome://accessibility

Toggle your "Global Accessibility Mode" to ON and see if this alleviates the problem.

I hope this information helps! :D

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Unable to see inside chrome://memory-redirect

Post by Support Team » Fri Sep 05, 2014 12:37 pm

Hello All,

Can´t find the answer to your question concerning test automation with Ranorex?

Learn about the features and get more information about Ranorex web test automation.
For more detailed Q&A, please feel free to contact our support team through [email protected].

Regards,
Markus
.
Image