Hi,
I have not yet updated to TC11.1 (still on 10.5), so this may be unrelated to your problem. However, I've had numerous issues with Chrome performance, and found that most of them were due to using the "contentText" property with the Find/FindChild methods. The issue was also compounded by the object's depth in the DOM relative to the parent object. For example, I had one Find statement that took about 4 minutes to locate the object in Chrome using contentText; after switching the property to use 'innerText' instead, it ran in about 5 seconds (similar to FF & IE). In that example, the depth was 10 levels below the parent object on a complex page. After some experimenting I found that for each level deeper (relative to the parent object), over 20 seconds to the overall search time. In most cases I was able to simply convert the 'Find' to use the 'innerText' property (or 'idStr' if available, or some other property), and the Chrome performance has been OK for me since.
Here is another related post on the issue.
Otherwise, if this is not the issue, I'd suggest to try to limit the test to a single area, then check the Test Log timings compared between Chrome and FF to help narrow it down.
(btw, your screencast link has some extra characters at the end of it). For the Columns button, can you still spy the control? If not, you may need to update the TC browser patches (or disable the browser auto-updates and manually upgrade them when needed).
Hope that helps,
Brian
@brk9394
Thanks for the info! I'm now activly trying to avoid contentText, and I was using it everywhere. The odd thing, though, is that until the update the performace was much better, including using contentTexts. But still, thanks!
@TanyaGorbunova
I was running the tests in a windows VM used solely for these tests. There were no extensions enabled.
Hi Kroe761,
I would recommend that you contact our TestComplete Customer Care Team ( http://support.smartbear.com/product-list/ ) to troubleshoot this behavior. Several users have already complained about the slow performance in Chrome 45+TestComplete 11.1 in the Community. Our R&D team is trying to find the cause of this behavior. If you provided them with the steps to reproduce the issue, that would be awesome.
Thanks in advance.
