Run the base form without customizations. If they are not there then make
sure in your customization you are not only disposing but also dereference
the pointer obj=null; GC should clean it after that
sure in your customization you are not only disposing but also dereference
the pointer obj=null; GC should clean it after that
On May 15, 2012 11:43 AM, "Jeff Rogers" <jeff.rogers@...> wrote:
> **
>
>
> Jose,
>
> When running the Memory Leak Tester are we looking for objects that are
> still in a Live state after the form is closed? I have some objects that
> are still listed in the Memory Leak Tester after the form is closed, but in
> a Disposed state. Is this an issue?
>
> Thanks!
>
> --- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
> >
> > run your client with /memory
> >
> > mfgsys.exe /memory will show you a leak tester, may be helpful
> >
> > *Jose C Gomez*
> > *Software Engineer*
> > *
> > *
> > *checkout my new blog <http://www.usdoingstuff.com> *
> > *
> > *T: 904.469.1524 mobile
> > E: jose@...
> > http://www.josecgomez.com
> > <http://www.linkedin.com/in/josecgomez> <
> http://www.facebook.com/josegomez>
> > <http://www.google.com/profiles/jose.gomez> <
> http://www.twitter.com/joc85>
> > <http://www.josecgomez.com/professional-resume/>
> > <http://www.josecgomez.com/feed/>
> > <http://www.usdoingstuff.com>
> >
> > *Quis custodiet ipsos custodes?*
> >
> >
> >
> > On Thu, Jan 26, 2012 at 2:43 PM, James <jamescompton@...> wrote:
> >
> > > **
> > >
> > >
> > >
> > >
> > > Event handlers are usually the first culprit I look at with C# and
> memory
> > > leaks.... if you add an event assignment by addition (+=) you must
> have a
> > > (-=) before you dispose or you get a leak and the object will never
> enter
> > > gen(2) state since its reference may never get cleared. These are real
> easy
> > > to create and sometimes hard to find. I also wouldn't rule out Epicor
> is
> > > not detaching everything cleanly either.
> > >
> > > Windbg allows you to attach to any .net process and poke around inside
> the
> > > heap. It's ugly though and seems to make me question GC in managed
> code.
> > > I'd only go that route in desperation.
> > >
> > > Good luck...
> > >
> > >
> > > --- In vantage@yahoogroups.com, Jose Gomez <jose@> wrote:
> > > >
> > > > We've experienced this before but usually as loing as you dispose =
> null
> > > > all your custom stuff its ok, however .NET is leaky and specially the
> > > > Epicor kind. If I remember correctly there is /CONFIG option you cna
> pass
> > > > to the client which will show all not disposed obkects.
> > > >
> > > > I'll see if I can remember.
> > > >
> > > > *Jose C Gomez*
> > > > *Software Engineer*
> > > > *
> > > > *
> > > > *checkout my new blog <http://www.usdoingstuff.com> *
> > > > *
> > > > *T: 904.469.1524 mobile
> > > > E: jose@
> > > > http://www.josecgomez.com
> > > > <http://www.linkedin.com/in/josecgomez> <
> > > http://www.facebook.com/josegomez>
> > > > <http://www.google.com/profiles/jose.gomez> <
> > > http://www.twitter.com/joc85>
> > > > <http://www.josecgomez.com/professional-resume/>
> > > > <http://www.josecgomez.com/feed/>
> > > > <http://www.usdoingstuff.com>
> > > >
> > > > *Quis custodiet ipsos custodes?*
> > > >
> > > >
> > > >
> > > > On Thu, Jan 26, 2012 at 2:17 PM, jim.taylor3 <jim.taylor3@> wrote:
> > > >
> > > > > **
> > >
> > > > >
> > > > >
> > > > > Has anyone else experienced and resolved C# memory leaks with their
> > > > > customizations.
> > > > >
> > > > > The behavior we are experiencing is that each time the form is
> opened
> > > and
> > > > > closed, memory is promoted to Gen 2 of the stack and the # of
> handles
> > > > > steadiliy increases so that, over time we hit an OOM error.
> > > > >
> > > > > We have tried, dispose() and setting to null, wrapping in using
> > > statements
> > > > > and forced Garbage collections. None have had any impact, good or
> bad.
> > > > >
> > > > > Any suggestions?
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
[Non-text portions of this message have been removed]