w3wp memory over 1G causing exception

The w3wp.exe process' memory seems to go from below 200M to over 1G
with no warning, causing Memory.Exception.

I have searched around and read some answers, and most seem very
vague. They say to "debug." Well duh, that is what I am trying to
do, and there appears to be issues with my code or third party
controls, but I need to pin point the culprits in my code. I can't
use my Visual Studio.NET to "debug" obviously, so what are people
saying when they say to "debug"?

What "debugging tools" are there I can use? Thanks.

Version - .NET 1.x
OS - 2003Search on "ADplus" which can capture a snapshot of the process and threads on
a crash.

Otherwise, this is usually because managed - and particularly unmanaged
(connections, file handles, sockets, etc) resources aren't being properly
disposed after use.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder(BETA): http://www.blogmetafinder.com
"David C" wrote:

Quote:

Originally Posted by

The w3wp.exe process' memory seems to go from below 200M to over 1G
with no warning, causing Memory.Exception.
>
I have searched around and read some answers, and most seem very
vague. They say to "debug." Well duh, that is what I am trying to
do, and there appears to be issues with my code or third party
controls, but I need to pin point the culprits in my code. I can't
use my Visual Studio.NET to "debug" obviously, so what are people
saying when they say to "debug"?
>
What "debugging tools" are there I can use? Thanks.
>
Version - .NET 1.x
OS - 2003
>
>

On Jun 26, 6:51 am, Peter Bromberg [C# MVP]
<pbromb...@.yahoo.yabbadabbadoo.comwrote:

Quote:

Originally Posted by

Search on "ADplus" which can capture a snapshot of the process and threads on
a crash.
>
Otherwise, this is usually because managed - and particularly unmanaged
(connections, file handles, sockets, etc) resources aren't being properly
disposed after use.
-- Peter

All of my objects are managed, and I do not use any unmanaged code.
So I am at the mercy of Garbage Collector, am I not? So how can I
debug GC to see how it dispose (or doesn't) resources.
On Jun 26, 11:51 am, "Juan T. Llibre" <nomailrepl...@.nowhere.com>
wrote:

Quote:

Originally Posted by

re:
!The rapid memory growth is happening on the production server, so how
!will I attach Visual Studio.NET to debug it while scores of users are on it?
>
You shouldn't be debugging on the production server, anyway.
>
What is stopping you from debugging on your development server ?

I have no idea what is that the users do that triggers rapid memory
growth.
re:
!I have no idea what is that the users do that triggers rapid memory growth.

You have available all sorts of performance counters
which can give you pointers regarding what the problem is.

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en espaol : http://asp.net.do/foros/
======================================
"David C" <profnachos@.gmail.comwrote in message news:1182888533.069793.37390@.m37g2000prh.googlegro ups.com...

Quote:

Originally Posted by

On Jun 26, 11:51 am, "Juan T. Llibre" <nomailrepl...@.nowhere.com>
wrote:

Quote:

Originally Posted by

>re:
>!The rapid memory growth is happening on the production server, so how
>!will I attach Visual Studio.NET to debug it while scores of users are on it?
>>
>You shouldn't be debugging on the production server, anyway.
>>
>What is stopping you from debugging on your development server ?

>
I have no idea what is that the users do that triggers rapid memory
growth.
>