Natsuki
Occasional Contributor
Joined 2 years ago
User Profile
User Widgets
Contributions
Re: Unable to load content document in Object Browser
We have a similar problem with you. We can not recognize any object in Chromium Embedded Framework since updated to version 15.58/15.59. The whole page becomes one single object and have a Error when using object spy. We now rollback to 15.57 by uninstall first and install a 15.57 Installation package.( TestComplete1557.exe)Re: Why my APP's memory usage Continuously rising when TestComplete is searching for/operating items?
Tryed useing another test tool such as Ranorex, no memory leak occurs in my app while using cilck method or search method Ranorex provides. So I thought its neither me nor Delphi+CEF but TC's support on CEF causes this problem. Memory leak occurs every time in TC when searching for any object in CEF(11.4) while don't leak when searching for any Delphi objects.Why my APP's memory usage Continuously rising when TestComplete is searching for/operating items?
I am testing a Delphi+CEF App. Version of my TC is 15.54.3.7 x64.Langue is Python. Now ,assume that 'AButton' is mapped in Namemapping with 'idstr=abuttonid' Case 1.When the button is actually not on the app, I do 'Aliases.SomeApp.AButton.Click()',my app's Memory useage rised very fast for about 1,300KB per second until TC throws an error of not found the item. Case 2.The button is not on the app still, When I do "Aliases.SomeApp.WaitAliasChild('AButton',200)", my app's Memory useage rised very fast just like case 1 until timeout is reached. Case 3. When I was cycling 100 times 'Aliases.SomeApp.AButton.Click()' I found that my app's Memory useage rised for about 1000 kb. Also, 'Click' after 'RefreshMappingInfo' method will also cause memory leak to my App. I want to test whether there is small memory leak in my App but the memory leak of every action in TC disturbs me a lot. Is there really memory Leak on TC, or I did something wrong? Why operates in TC can cause memory usage of my App greatly rise? Thanks for reading and sorry for my poor English.
