Forum Discussion

sdahiya's avatar
sdahiya
Occasional Contributor
9 years ago

Testcomplete resource problem

Hello SMARTBEAR Team,   From last some weeks, we are facing a new testcomplete resource problem. The scenario is following: we have a testsuite which include 7-8 projects in it. The size of 5 pr...
sdahiya's avatar
sdahiya
Occasional Contributor
9 years ago

Hello Tanya,

 

Yes, I also tried to open the project in Testcomplete 12.0

but I don't see any big difference.

 

By the way currently we are using Testcomplete 11.31.

  • JuliaBernikova's avatar
    JuliaBernikova
    SmartBear Alumni (Retired)
    9 years ago

    Hi Sdahiya,

     

    I suggest that you check the size of the Name Mapping file (the NameMapping.tcNM file in the <project name>\NameMapping folder). In case it is too large, the problem is most probably with the code completion data. So, try turning on the Do not store Code Completion data option in the Name Mapping editor. For more information on this option, please refer to the "Saving Information on Methods and Properties of Mapped Objects" article.

     

    Let us know whether this helps.

    • sdahiya's avatar
      sdahiya
      Occasional Contributor
      9 years ago

      Hi Julia,

       

      Thanks for your information but unfortunately it is not a Namemapping problem.

      Even the name mapping settings are configured same (Do not store Code Completion data is set in option) as it is mentioned in the link.

       

      • joseph_michaud's avatar
        joseph_michaud
        Moderator
        9 years ago

        Are you saying that the size of disk space taken by some projects is very large or that TestComplete consumes a lot of memory when opening the project?  (or both?)

         

        If you have a lot of log files that you don't need, remove them from the project(s).  If you don't need visualizer images, turn that off in your projects.

         


        It might be that a particular project is consuming lots of memory.  If you want to do some investigation, make a backup of your project suite and then..

        ...try 'removing' all but one of your projects from your project suite and then close and reopen the project suite to see how that affects the amount of memory used.  (Use 'remove' not 'delete'.)  Add back the projects into the project suite as 'existing items' one by one to see how memory usage is affected.

         

        Is there one project causing the problem?