Forum Discussion
AlexKaras
12 years agoCommunity Hero
Hi Curt,
Yes, you are correct.
However, this problem can also be explained as a consequence of the improved TestComplete performance :) : if the problematic object (or its parent) was created by some page script code, then when the object becomes obsolete it is not destroyed immediately by some clean-up code (like it is implemented in native desktop applications), but after some time by the garbage collector process. So, it might be that garbage collector was able to clean up the object when TestComplete worked slower, but just don't have enough time now.
Yes, you are correct.
However, this problem can also be explained as a consequence of the improved TestComplete performance :) : if the problematic object (or its parent) was created by some page script code, then when the object becomes obsolete it is not destroyed immediately by some clean-up code (like it is implemented in native desktop applications), but after some time by the garbage collector process. So, it might be that garbage collector was able to clean up the object when TestComplete worked slower, but just don't have enough time now.