Apr 19, 2012, 11:16 AM
[CLOSED] Memory leaks when used in System.Windows.Controls.WebBrowser instance
We have a WPF desktop application which uses a System.Windows.Controls.WebBrowser instance to load a web application.
Once the web application is closed the desktop application disposes existing System.Windows.Controls.WebBrowser instance and make the reference as null if any.
Our web application uses ext.net controls. When this application is loaded in System.Windows.Controls.WebBrowser instance and closed, still the memory acquired by System.Windows.Controls.WebBrowser instance is not fully released. The web application has to be relaunched again and again in desktop application and everytime unreleased unmanaged memory gets increased. We did a sample application which uses ext.js but we didn?t experience this memory leak behavior. Here the web browser is Internet Explorer 8.
Please help to solve this memory leak issue.
Once the web application is closed the desktop application disposes existing System.Windows.Controls.WebBrowser instance and make the reference as null if any.
Our web application uses ext.net controls. When this application is loaded in System.Windows.Controls.WebBrowser instance and closed, still the memory acquired by System.Windows.Controls.WebBrowser instance is not fully released. The web application has to be relaunched again and again in desktop application and everytime unreleased unmanaged memory gets increased. We did a sample application which uses ext.js but we didn?t experience this memory leak behavior. Here the web browser is Internet Explorer 8.
Please help to solve this memory leak issue.
Last edited by Daniil; Jun 15, 2012 at 9:50 AM.
Reason: [CLOSED]