Re: Memory Leak
- From: "Peter" <czupet@xxxxxxxxxxxxx>
- Date: Thu, 19 Jun 2008 12:21:17 -0500
"Cor Ligthert[MVP]" <notmyfirstname@xxxxxxxxx> wrote in message
news:195BA553-ECD7-4241-947B-3C73E8021294@xxxxxxxxxxxxxxxx
Peter,
Always the first questions on Memory Leaks in the dotnet newsgroup
How do you know that there is a Memory Leak?
Cor
"Peter" <czupet@xxxxxxxxxxxxx> schreef in bericht
news:OSW0fZc0IHA.3756@xxxxxxxxxxxxxxxxxxxxxxx
I am using VS2008.
I have a Windows Service application which creates Crystal Reports. This
is a multi theaded application which can run several reports at one time.
My problem - there is a memory leak someplace. I can not detect the
memory leak by running several reports by hand, but when I run tha app as
a servrice and process few hundred reports there is significant memory
leak. The application can consume over 1GB of memory where it should not
go over 200 mb. I have few other applications that use Crystal Reports
and those applications do not have memory leak, the big difference is
those applications are single threaded.
My question is are there any free tools I can use to find the memory
leak?
I have tried http://www.softprodigy.com but I could not get it to work it
just locks up.
Thank You
Peter
I do not know if it's the memory leak - that's what I am trying to find out.
The reason I am starting with this assumption is because when I look at the
"Mem Usage" in the Windows Task Manager the memory keeps growing and never
ever goes down and eventually the system goes to a craw until I restart the
application. Plus my other simullar applications when they run the "Mem
Usage" goes up and down and eventually goes back to the almost original
starting number when the applications is not processing anything.
.
- References:
- Memory Leak
- From: Peter
- Re: Memory Leak
- From: Cor Ligthert[MVP]
- Memory Leak
- Prev by Date: Re: How delete rows from DataTable and avoid "no row at position" error?
- Next by Date: Setting the port for IIS programatically
- Previous by thread: Re: Memory Leak
- Next by thread: RE: Memory Leak
- Index(es):
Relevant Pages
|