Forum Discussion

vincent_goude's avatar
vincent_goude
Occasional Contributor
11 years ago
Solved

Oversized Namemapping

Hi, we are having trouble managing the size of our Namemap file.

It grows unexpectandly from 1Mo to more than 130Mo with only a hundred new objects.

It seems that the Namemap was corrupted by concurrent access on the projet.

Did anybody encountered this issu before?



Is there a way to repair or monitor the Namemap file?
  • TanyaYatskovska's avatar
    TanyaYatskovska
    11 years ago

    Hi Vincent,


     


    There was a similar issue in TestComplete 9.0. It was resolved. Please make sure that you are using the latest TestComplete version - v. 9.31.


     

4 Replies

Sort By
  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)
    11 years ago

    Hi Vincent,


     


    There was a similar issue in TestComplete 9.0. It was resolved. Please make sure that you are using the latest TestComplete version - v. 9.31.


     

  • vincent_goude's avatar
    vincent_goude
    Occasional Contributor
    11 years ago
    Sorry but we are currently in TC last version 9.31

    Project is accessed in shared mode and and the name map is still growing with each addition and deletion.

    It has now more than 500 Mo.

    Panic mode on!!
  • vincent_goude's avatar
    vincent_goude
    Occasional Contributor
    11 years ago
    Hi Tanya, the issue is definitely related to Shared network projet.

    We solved it by Merging the corrupted NameMap with a clean one.

    The Name Map went down from 174 Mo down to 1,4Mo.

    It seems that Shared project namemap store temporary copy of elements.

    The number of Child Item stored went down from 471773 <Child> node to 4113.



    So problem solved by Merge.

    We won't use the Shared project feature anymore to edit/script.