We have a page where table is created with AJAX technology by ASP.NET. Table is invisible until all its rows are loaded, and the problem is that number of rows is very big, e.g. 5000, and each row has 9 columns. We wait until page is loaded, checking page's `Busy` property with delays. After that property becomes True, we call WaitItem() method to get table object and determine if it exists, and that's where TC hangs. It starts to eat memory, allocating up to 1.2 GB (when 2 GB of total physical and swap memory is available).
Is there any way to solve that problem?
Project configuration includes Web + MSAA, language is C# Script.
We will try to improve working with Web pages that have a great number of objects in future versions of the tool.
In the meantime, the only solution I can suggest is using native methods and properties of the Web page's objects in order to avoid building an object tree in TestComplete. You can find a description of this approach in the following thread of the official TestComplete newsgroup: http://www.automatedqa.com/forums/d.cgi?...13282&utag=