SPY memory leak when detecting elements in Chrome

Ranorex Studio, Spy, Recorder, and Driver.
mmackay23
Posts: 14
Joined: Wed Sep 01, 2010 4:36 pm
Location: Dundee, Scotland
Contact:

SPY memory leak when detecting elements in Chrome

Post by mmackay23 » Wed May 22, 2013 12:21 pm

When using SPY for Chrome elements detection, the application freezes and task manager shows memory increases rapidly indicating some kind of leak. This happens after I track an element then modify the path.

OS: Windows 7 64 bit
Chrome: Version 27.0.1453
SPY: 4.0.3.22982

Eventually the app crashes or gets stuck with not responding.
Martin Mackay
Automation Test Analyst

"To improve is to change, to be perfect is to change often."
-Winston Churchill

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA
Contact:

Re: SPY memory leak when detecting elements in Chrome

Post by Support Team » Thu May 23, 2013 4:14 pm

Hello,

Thank you for reporting this issue.
Unfortunately I cannot reproduce it. Are you using a specific website when the issue occurs?
Could you please give me more information about this issue?
Thank you!

Regards,
Bernhard

mmackay23
Posts: 14
Joined: Wed Sep 01, 2010 4:36 pm
Location: Dundee, Scotland
Contact:

Re: SPY memory leak when detecting elements in Chrome

Post by mmackay23 » Fri May 24, 2013 12:32 pm

Hi Bernhard,

It is when the SPY is trying to create the tree that the issue happens after the path has been modified. The web element is a text box on a popup.

Website: http://wwwdemo.systemmonitor.co.uk/dashboard


Thanks

Martin
Martin Mackay
Automation Test Analyst

"To improve is to change, to be perfect is to change often."
-Winston Churchill

User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA
Contact:

Re: SPY memory leak when detecting elements in Chrome

Post by Support Team » Mon May 27, 2013 2:33 pm

Hello,

Thank you for providing the application, but unfortunately I was not able to reproduce the issue. In my case the memory is constant.
We have released a new version last week. Please try to update Ranorex and check if the behavior is the same.
If the upgrade will not help I would suggest to make a web meeting in order to analyze the issue in more detail.
Thank you!

Regards,
Bernhard