Hi,
Its called GC_PRINT_STATS, not MONO_GC_PRINT_STATS.
Zoltan
On 9/16/05, Thorsten Schuett <[EMAIL PROTECTED]> wrote:
> On Thursday 15 September 2005 19:15, Paolo Molaro wrote:
> > On 09/15/05 Thorsten Schuett wrote:
> > > I "ported" a simulation from Visual C# beta 2 to mono this week. You
> > > can't really call it porting, because I only had to remove references to
> > > Stopwatch. But anyway, thanks to all of you for making it so easy.
> > >
> > > It is a long running application, therefore I used an IA64 at work.
> > > Almost everything worked without any hiccups. But after about 12h the
> > > memory consumption was up to 4GB. In the beginning it needed only about
> > > 50MB. In my
> >
> > Set the MONO_GC_PRINT_STATS env var:
> >
> > MONO_GC_PRINT_STATS=1 mono program.exe
> Are you sure about this flag? It doesn't seem to have any effect. google shows
> only two hits in nemerle. Just for the information, I am running 1.1.9.
>
> > and see if it's the GC heap that increases so much. If it doesn't
> > crease beyond a reasonable amount, we may have an unamanged memory leak.
> > Try running also on x86 and see if you still get the leak.
> > If it doesn't happen, it may be an unmanaged memory leak in the port.
>
> Thorsten
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
