"Alvin Bruney [MVP]" wrote:

> you've got a memory leak somewhere. you may want to try using the .net
> profiler to see what is goin g on.
>
> > When I run stress tests on my .NET application, after several hours I
> > often get a Windows dialog box that appears in the System event log
> > that states the following.
> >
> > "Application popup: Windows - Virtual Memory Minimum Too Low: Your
> > system is low on virtual memory. Windows is increasing the size of
> > your virtual memory paging file. During this process, memory requests
> > for some applications may be denied. For more information, see
> > Help..."
> >
> > After I click on this dialog box once, I do not see it again until I
> > restart the process with a fresh boot, etc...
> >
> > Question: Is this normal? Or, can this be normal?
> >
> > Question: Does this imply a memory leak? Or, is it possible that this
> > is just how .NET works?

"Frank" <franknewsgroups@yahoo.com> wrote in message
news:1513accc.0403190937.63f05b50@posting.google.com...
> When I run stress tests on my .NET application, after several hours I
> often get a Windows dialog box that appears in the System event log
> that states the following.
>
> "Application popup: Windows - Virtual Memory Minimum Too Low: Your
> system is low on virtual memory. Windows is increasing the size of
> your virtual memory paging file. During this process, memory requests
> for some applications may be denied. For more information, see
> Help..."
>
> After I click on this dialog box once, I do not see it again until I
> restart the process with a fresh boot, etc...
>
> Question: Is this normal? Or, can this be normal?
>
> Question: Does this imply a memory leak? Or, is it possible that this
> is just how .NET works?
>
> Thanks,
>
> Frank

"Alvin Bruney [MVP]" <vapor at steaming post office> wrote in message news:<OSuf4rfDEHA.712@tk2msftngp13.phx.gbl>...
> you've got a memory leak somewhere. you may want to try using the .net
> profiler to see what is goin g on.
>

> Does anyone have any suggestions on how to analyze a .NET application
> for possibly 1 or more small memory leaks? When I look at the number
> of C# objects in-use, that all looks fine.

"Frank" <franknewsgroups@yahoo.com> wrote in message
news:1513accc.0403201432.1e3df254@posting.google.com...
> "Alvin Bruney [MVP]" <vapor at steaming post office> wrote in message
news:<OSuf4rfDEHA.712@tk2msftngp13.phx.gbl>...
> > you've got a memory leak somewhere. you may want to try using the .net
> > profiler to see what is goin g on.
> >
>
> I am using the .Net Memory Profiler (or shall I say living in it), but
> I do not see any obvious leaks -- all of those leaks I already fixed
> ;)
>
> This is a managed/unmanaged application.
>
> Does anyone have any suggestions on how to analyze a .NET application
> for possibly 1 or more small memory leaks? When I look at the number
> of C# objects in-use, that all looks fine.
>
> It looked like the XMLSerializer was leaking, and so I worked around
> that. Does anyone know 100% if the .NET 1.1 actually had a memory
> leak in the XMLSerializer? -- I'm basing my comments on various
> newsgroup posts I've found, and not on any official statements from
> Microsoft.
>
> Frank

Frank wrote:

> When I run stress tests on my .NET application, after several hours I
> often get a Windows dialog box that appears in the System event log
> that states the following.
>
> "Application popup: Windows - Virtual Memory Minimum Too Low: Your
> system is low on virtual memory. Windows is increasing the size of
> your virtual memory paging file. During this process, memory requests
> for some applications may be denied. For more information, see
> Help..."
>
> After I click on this dialog box once, I do not see it again until I
> restart the process with a fresh boot, etc...
>
> Question: Is this normal? Or, can this be normal?
>
> Question: Does this imply a memory leak? Or, is it possible that this
> is just how .NET works?
>
> Thanks,
>
> Frank