Memory leakage


Author
Message
Danny Doobay
Danny Doobay
StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)StrataFrame User (208 reputation)
Group: StrataFrame Users
Posts: 40, Visits: 333

I have a maintenance form with two text boxes and a dropdownlist (See attachment).  All of the controls are bound toBO. Dropdownlist populationType is BusinessObject and it fill the data from amethod.

 

I am using enterprise server and this maintenance form fetchthe data from there.

 

Here is the issue: Before I open the maintenance form memorytaken by the application is 114.6 MB and as soon I open the form it was 127.1and when I close the form it was 120.2 MB. I did this many time to see what ishappening and here are the result:

Before Open ==> ASAP Opened ==> After Closed

114.6 ==> 127.1 ==> 120.2

120.2 ==> 129.8 ==> 123.1

123.1 ==> 126.8 ==> 119.9

119.9 ==> 133.1 ==> 126.1

 

It is happening to all the maintenance form and theapplication becoming a memory

 hog.

 

Is there any way I can fix this?


Attachments
Maintenance Form.JPG (251 views, 25.00 KB)
Reply
Trent Taylor
Trent Taylor
StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 6.9K
Just to add to Keith, we spend a fair amount of time sending our code through profilers, such as the .NET Memory Profiler.  Everythign that Keith said was correct in regards to looking at the Task Manager, etc.  Even if you force a garbage collection, the task manager may still not reflect what is really going on.

Tracking down memory leaks is a pain, but the tool that we use most often now is .NET Memory Profiler (http://memprofiler.com/) and you can see what references, handlers, etc. are being left open as well as objects that are not being disposed.  Sometimes it can be a very complicated process to track down the issue, and other times very obvious once you see it in the profiler, but in any case, you need a tool like this to really get to the bottom of it.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search