Hello,
We are working on automating memory testing and ran into a problem where it appears that the automation interfaces are holding references to controls within our application. This gives us a bogus reading in the memory profiler. After investigating, it appears as though the UIAutomation bridge is using remoting to retrieve references to the controls in our application.
We also found that putting in a Thread.Sleep for 2 minutes before taking each memory snapshot fixes this issue.
My question is, can you confirm that remoting is being used to communicate with controls? And if so, is there any way to set the timout to sever the connection on command?
Thanks,
Mike
Mike Watkins
We are working on automating memory testing and ran into a problem where it appears that the automation interfaces are holding references to controls within our application. This gives us a bogus reading in the memory profiler. After investigating, it appears as though the UIAutomation bridge is using remoting to retrieve references to the controls in our application.
We also found that putting in a Thread.Sleep for 2 minutes before taking each memory snapshot fixes this issue.
My question is, can you confirm that remoting is being used to communicate with controls? And if so, is there any way to set the timout to sever the connection on command?
Thanks,
Mike
Mike Watkins