Forum Discussion

bapilado's avatar
bapilado
New Contributor
14 years ago

TestComplete 8 locks up on flash application contain 30+ elements



I have this flash application that contains a frame with a large number of flash elements (buttons, texts, graphics). When TestComplete attempts to refresh its object browser, TestComplete hangs (locks up).    Although the amount is dynamic based on a data file, the amount of flash elements is always at the least 30. With any other frame of the flash application where the amount of flash elements are less, TestComplete functions as intended and does not hang. 



So my question is:

How many flash elements within a flash application can be detected by TestComplete?




1 Reply

Sort By
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Staff
    14 years ago
    Hi Ben,



    There is no limitation on the maximum number of objects - it depends more on the PC resources than on TestComplete. I suppose that the tool does not actually hang when there are many objects on a web page. Most probably, it just takes long to build/update the object tree. First of all, try using suggestions provided in the following technical paper - they can help you improve the objects recognition speed:


    Automated Test Performance Tips



    If the suggestions do not help, please follow the instructions below to help us collect more information about the problem:



    1. Download the Debugging Tools for Windows package from:


    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx


    and install it.



    2. When TestComplete and (or) the tested application hang(s), run two instances of WinDbg ("C:\Program Files\Debugging Tools for Windows\windbg.exe").



    3. Attach the first WinDbg instance to TestComplete's process and attach the second instance to the tested application's process (File | Attach to a Process).



    4. Type the following command in the Command window of the first instance of WinDbg:


    .dump /m "C:\TCDump.dmp"


    and press Enter.



    5. Type the following command in the Command window of the second instance of WinDbg:


    .dump /m "C:\AppDump.dmp"


    and press Enter.



    6. Click Go on the WinDbg toolbar (or press F5) in both WinDbg instances. Wait for one minute and click Break (or press "Ctrl + Break") in both instances of WinDbg.



    7. Repeat steps 4 and 5 to save another set of dump files with different file names.



    8. Without a delay, repeat steps 6 and 7 two more times.



    9. Send us all of the dump files created in the steps above.



    Thanks in advance.