How to get around the memory leak in the .NET Webbrowser control?

This leak appears to be a leak in unmanaged memory, so nothing you do in your process is going to reclaim that memory. From your post I can see that you've tried avoid the leek quite extensively and without success. I would suggest a different approach if feasible.

Create a separate application that uses web browser control and start it from your application. Use the method described here (stackoverflow.com/questions/4608130/how-...) to embed newly created application within your own existing application. Communicate with that application using WCF or .

NET remoting. Restart the child process from time to time to prevent it from taking to much memory. This of course is quite complicated solution and the restart process could probably look ugly.

You might maybe resort to restarting the whole browser application every time user navigates to another page.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.