This is a migrated thread and some comments may be shown as answers.

memory leak when connecting to windows and then closing

5 Answers 68 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Jem asked on 02 Jun 2015, 02:20 PM

testopenwindow.zip

Using Telerik Test Framework 2015.1.319.0

I have a wpf application to test which opens windows in a list-> detail paradigm.

Each detail window opens a new wpf window which can be wrapped by WpfApplication.WaitForWindow(caption, windowTimeout).

Each window is closed using:

WpfWindow.Window.DetachWrappedWindow();
WpfWindow.Window.Close();

Using a 32 bit test application this will open and close about 50 windows before terminating with an out of memory exception.

Using editbin /LARGEADDRESSAWARE $(TargetPath) to increase accessible memory allows about 250 iterations before the exception.

On examination it seems that the telerik test framework is not releasing resources when a WaitforWindow wpfWindow is closed.

If the (detail) wpfwindow does not do any RefreshVisualTrees() or any .Find() operations then the resources do not run out.

The more complex the detail window, the more resources are lost.

I have attached a sample application which uses a similar model - showing the resources not being released. If you run the application (without debugger!) and simultaneously run perfmon looking at working set and working set peek - you can see it inexorably creeping up. With such a small application you wont actually get the out of memory condition. However this is preventing some important test scenarios for my clients.

Please can you advise?

Regards

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting & Mocking

Automated Testing

CMS

UI/UX Tools

Debugging

Free Tools

memory leak when connecting to windows and then closing

5 Answers, 1 is accepted