Forum Discussion

liangn's avatar
liangn
Occasional Contributor
14 years ago

it hangs in about two hours even while the Sample Hello is carried out

Hello all,



my testComplete(version 5.15.561.7) stops always about 2 hours after starting a test. Even with the sample of "Hello". When I tried to run the sample in a loop (500 times), it stoped somewhen. By using windbg a breakpoint is found at ntdll.dll.



please, is there any solution for the problem?



thanks a lot.

Nan





Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path.           *

* Use .symfix to have the debugger choose a symbol path.                   *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

Windows XP Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: SingleUserTS

Machine Name:

Debug session time: Tue Jun  1 10:41:42.000 2010 (UTC + 2:00)

System Uptime: not available

Process Uptime: 0 days 1:42:36.000

................................................................

................................................................

..........................................

This dump file has a breakpoint exception stored in it.

The stored exception information can be accessed via .ecxr.

eax=7ffdf000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005

eip=7c90120e esp=0166ffcc ebp=0166fff4 iopl=0         nv up ei pl zr na pe nc

cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000246

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll -

ntdll!DbgBreakPoint:

7c90120e cc              int     3

1 Reply

Sort By
  • Dmitry_Nikolaev's avatar
    Dmitry_Nikolaev
    Staff
    14 years ago

    Hi,





    Most likely, you are facing this issue due to the out of memory problem. This can be caused by a huge Test Log. 





    To reduce the size of the log, please follow the steps below:





    1. Call the Log.LockEvents method in the very beginning of your test to prevent TestComplete from posting unnecessary event messages. Please see the Log.LockEvents help topic for more information on the Log.LockEvents method.





    2. Do not store screenshots in the BMP format. I recommend that you use the PNG format because it saves images in the same quality, but uses less memory. Please see the Specifying Log Images Format help topic to learn how to change the format of screenshots stored in the Test Log.





    This should solve the memory problem.