Re: Memory Leak?

Dave Vorgang <[email protected]>
Newsgroups gmane.comp.windows.devel.dotnet.advanced
Message-ID <34BDEF4FDF97EC46B7565B38A5F93FF702378FAB58FE@MSDMAIL.medford.k12.or.us>
I changed it to:
        Do
            System.Windows.Forms.Application.DoEvents()
            Thread.Sleep(55)
            GC.Collect()
        Loop Until _KeyEntered >= 0

This helped but it still increased Mem Usage as time went on.

Any help on fixing this would be greatly appreciated.

Thanks,

Dave Vorgang
Senior Programmer / Analyst
Medford School District - Information Technology
(541) 842-1021
mailto:[email protected]

-----Original Message-----
From: Discussion of advanced .NET topics. [mailto:[email protected]] On Behalf Of Mark Hurd
Sent: Monday, December 01, 2008 3:16 PM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Memory Leak?

On Tue, Dec 2, 2008 at 9:38 AM, Steve Johnson <[email protected]> wrote:
> Likely, the problem is recursion.  Each call to DoEvents pumps messages,
> which causes your VREADFIELDS function to be called from within itself.
> Each call allocates another stack frame.  You'll eventually run out of stack
> space and crash with a StackOverflowException.

I agree that it is not due to the code sample provided in isolation.
Whenever we need an idle loop we use a similar loop (with Sleep(55)),
and when it is worth suggesting we know it would be a good time to do
a GC.Collect we include that too.

Regards,
Mark Hurd, B.Sc.(Ma.)(Hons.)

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.