It is a Keyword driven tests .
The test did work.
My Test Complete is updated.
I have raised a support case and submitted the Memory dump.
Lets see the real issue!
Thank You!
I have a support case open for a similar situation. It's not so much that it can't find the object but that there's a lot of "find" logic happening throughout my project. We have the Extended Find flag set on some modal windows, we're using findChild and FindAllChildren in some situations, WaitForProperty against those modals which does some finding internally... And TC craps out.
What I've done that works around this is minimize the use of Extended Find. I'm slowly re-mapping my UI objects where, unless ABSOLUTELY necessary, I don't use Extended Find... and most DEFINITELY not on modal windows that I need to detect. This has reduced the instance of this crashing.
My response from SmartBear is that there's a stack overflow in the threading somewhere between different areas of the application. They have a number of memory dumps from me (I used ReportGenerator and reproduced the problem and sent them the resulting report as well). So... if you can send them similar information, it might help both of us out so that they can see similarties between our situations.
