[DUG] Memcheck

[Jeremy North]

Exactly. I can't find it yet but it isn't recommended to trim your
working set continually. It can slow future memory allocations in your
application.

If people _think_ you app is running with too much memory - tell them
to Minimize and Maximize the app to see a true indication, and then
explain to them about how the OS allocates memory - hopefully they
will be asleep after the first sentence...

On 12/1/05, Kyley Harris <kyleyharris at gmail.com> wrote:
> Does anyone actually care about such matters in real working life?
>
> I mean, it operating system managed memory. When it needs it, it takes it
> back. One would hope and
> presume that it is managing it in such a way as to appear efficient for
> speed and allocations by not retaking
> memory pointers back from an application that may well want them again.
>
> On Thu, 01 Dec 2005 14:21:17 +1300, Stefan Mueller
> <muellers at orcl-toolbox.com> wrote:
>
> > You can do it manually (compressing the memory-creep) by calling:
> >
> > if Win32Platform = VER_PLATFORM_WIN32_NT then
> >     SetProcessWorkingSetSize(GetCurrentProcess, $FFFFFFFF, $FFFFFFFF);
> >
> > This has the same effect like a minimize/maximize.
> >
> > Cheers,
> > Stefan
> >
> >
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>