Thanks Ryan. I was actually already starting my search below the Page. I already had the page and found a panel a few levels below the page, then searched within this panel to find the object. I have not yet tried switching to .Find instead of .FindChild but will give it a shot. I had also experimented with eliminating the refresh, but this had little impact on the performance I saw and caused me some other issues due to the pages having dynamic content.
I will definitely need to look into the CollectGarbage() for a different TestComplete project I run against a WPF client that seems to have memory leaks.
All this having been said, the Developers added some Identifiers where possible so I switched the Find to look for idStr rather than contentText and it went from 13 sec to about 1 sec in Chrome. In Firefox it is about 0.3 sec whether looking at idStr or contentText.
It seems to me that there is a bug (or at least major limitation) to using Find by contentText in Chrome.
