I would suggest contacting support as well.
If it is a bug in Test Complete the odds are that they will not be able to give you an immediate fix no matter what you do, but this may lead to a fix for others later down the road.
In the mean time the simplest solution (and I know it's probably easier said than done) take stuff out of your tests until you can narrow down the issue.
Alternatively you can try reverting to a previous version of Test Complete to see if the error still occurs.
Follow the standard troubleshooting method...etc..etc..etc..
Hope that helps :)
Hi Ryan,
Thanks for your reply.
I'm jsut asking for something that should be somehow documented. I just want to understand what causes the "out of system resources" pop up. If I had that, I can probably work on a solution myself.
On the other hand... if they are not able to provide a solution... why should I continue paying for support??
Cheers,
Leandro
I suppose you should try to take a look at number of Handles, Threads, USER Objects, GDI Objects consumed by TestComplete and AUT using Windows Task Manager (go to View | Select Columns menu in Task Manager and select those counters).
Hi Dgnov,
I did monitor those parameters and they don't really seem to be out of control. Maybe by the time I get to see the message those are back to normal.
In any case there's nowhere to change that inside TestComplete, so it'd be only useful for TC devs maybe.
Interesting to analyse though, so I'm planning on monitor those from the tests themselves in case it helps.
Cheers,
Leandro
