Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When I run my app targeted to .Net 3.5 it has massive memory leaks. 50mb every time I assign a UserControl to a local ref. I only ever create one instance of each UserControl. If I compile and run the same code targeted to .Net 4.0 everything runs fine hovering around the 50mb mark.
Is this a known isue with 3.5? I.e. it’s not usable in prod?
/My clients only have 3.5 and won’t be moving to 4.0 for awhile so i don’t have the easy option
Memory Leak Hotfixes for WPF 3.5 SP1
http://www.infoq.com/news/2010/06/WPF-Memory-Leaks
In particular, have a look at these two hotfixes, which have been fixed in .NET 4.0, but are available as hotfixes to users of .NET 3.5:
http://support.microsoft.com/kb/967634
http://support.microsoft.com/kb/967328