Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 27 Sep 2013 11:58 by ADMIN
ADMIN
Plamen
Created on: 10 Apr 2013 08:20
Type: Bug Report
0
Memory leak in a console application which uses Telerik Testing Framework to automate WPF application. 
I have been investigating this issue and can reproduce the problem with a minimal console application which starts a simple WPF window application and then closes it again. It does not exhibit this behavior simply opening and closing the application. It does not exhibit the behavior when finding and clicking a WPF button. However it does exhibit it when finding a 3rd party control (but taking no further action on that control). The 3rd party control we are using is  an Actipro docking control.

To reproduce:
Sample WPF application and a sample Console application are attached to the internal bug description.
2 comments
ADMIN
Daniel Djambov
Posted on: 27 Sep 2013 11:57 
Telerik: In the original feedback item problem is that application is written in a way that does not clean up its memory properly and the operations in the thousands iterations are very fast, which stacks memory and at some point it crashes with Out of memory Exception. Unfortunately there is not much we can do with .Net Out Of Memory exceptions. These are errors that do not depend on the amount of physical and free memory, but rather is a bug how windows handles memory internally and copies it back and forth from physical memory into file cache. If during this operation memory manager reports the memory slot is empty, while it is currently being emptied and then another process tries to use this memory - then the exception occurs. You can find more details in this article http://blogs.msdn.com/b/ericlippert/archive/2009/06/08/out-of-memory-does-not-refer-to-physical-memory.aspx
Jem
Posted on: 29 Apr 2013 12:46 
Any progress on this yet?
Create an account Log In
View
Type
Status