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.
Actually I am working on real-time application with multiple threads.
While I am running my application memory is 65 Mb and if I open a child MDI form then memory increases to 85mb but if I close the child window then memory will still remains at 85mb.
I have used Dispose and I’ve already tried with GC.Collect(), but none of these solve my problems,
so I am little bit confused regarding this issue.
Can you please guide me regarding this?
Thanks in advance.
You need to get a good memory profiler.
There are a bunch of options:
Many cost money (except CLR Profiler) but usually have trial versions.
After you start your app (with the profiler attached), you need to take snapshots of the memory before the leak and after and compare them to see what is staying around.
It’s hard to say what the problem might be in your case, since there are many things that could be causing the problem.