|
-
Mar 18th, 2011, 08:02 PM
#3
Thread Starter
Member
Re: WebBrowser memory leak - is there any real solution?
...which in turn will force me to rewrite massive amount of code, not only I will have to handle postdata myself, I will also need to take care of the cookies. Not to mention the fact, that it will severely affect "quick peek into webbrowser" quasi-debugging I have to keep for users. And it seems that my another project that was based on saving actual rendering of the page is non-doable.
Damn -__ Guess I will have to look into this.
But since I got somebody's attention - is there any reason for WebBrowser to behave that way, or is it just a bug that magically got overseen for last 8 years of .NET development?
Last edited by amras666; Mar 18th, 2011 at 08:07 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|