From: Mr. Arnold on
mgdev wrote:
> In general, we do practice disposing of objects. But I'm sure we are not
> perfect and there could be some left behind. Assuming this is a lack of
> disposing of objects. Are there any tools that could help me find these
> objects? The reason I'm asking is, this application is very large (100+
> classes plus 100+ aspx pages) and will take a lot of time to go through line
> by line to find indisposed objects.
>
> Please let me know your thoughts.
>

If the w3wp.exe is not given a chance to recycle itself and is
constantly running because the server is too busy running applications,
then static and dynamic memory are going to held onto, and root
variables/objects are not released and memory usage grows.

Also Inetinfo.exe, and Dllhost.exe are IIS processes too that can also
cause memory usage issues too.

http://support.microsoft.com/kb/919790
From: Mark Rae [MVP] on
"mgdev" <mgdev(a)discussions.microsoft.com> wrote in message
news:CB0C046F-0AC8-4531-B9A8-46C794D0CFFF(a)microsoft.com...

[please don't top-post]


> In general, we do practice disposing of objects.

I'm afraid that's not good enough, and almost certainly your problem.

You need to dispose of *ALL* objects every time all of the time.

I would suggest you investigate the database connectivity first...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

From: mgdev on
Are there any tools that can help me identify what objects are not being
disposed? Or do I need to go line by line through the hundreds of pages to
find them?
From: Mark Rae [MVP] on
"mgdev" <mgdev(a)discussions.microsoft.com> wrote in message
news:E059763B-FCEE-416B-A929-686A829C2B97(a)microsoft.com...

> Are there any tools that can help me identify what objects are not being
> disposed?

None that are worth using, IMO...


> Or do I need to go line by line through the hundreds of pages to find
> them?

Pretty much.

As I mentioned, I'd start with your database connectivity first.

Luckily this is a small web app (100 classes and 100 aspx pages is tiny in
the general scheme of things), so it shouldn't take you too long...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

From: "Mr. Arnold" MR. on

"Mark Rae [MVP]" <mark(a)markrae.net> wrote in message
news:36391CA8-61AF-439A-A7AF-6E61C3553BD9(a)microsoft.com...
> "mgdev" <mgdev(a)discussions.microsoft.com> wrote in message
> news:E059763B-FCEE-416B-A929-686A829C2B97(a)microsoft.com...
>
>> Are there any tools that can help me identify what objects are not being
>> disposed?
>
> None that are worth using, IMO...
>
>
>> Or do I need to go line by line through the hundreds of pages to find
>> them?
>
> Pretty much.
>
> As I mentioned, I'd start with your database connectivity first.
>
> Luckily this is a small web app (100 classes and 100 aspx pages is tiny in
> the general scheme of things), so it shouldn't take you too long...
>

That also depends on what else is running on the machine that w3pc.exe is
servicing, which can tip it. We face that problem on the IIS server, because
of the client insists upon running this one application that forces
scheduled IIS Resets. They are too cheap to get a dedicated Web server to
run this application.