[DUG] Monitoring Memory use
Myles Penlington
myles at ams.co.nz
Thu Jun 28 15:23:03 NZST 2007
Neither are really that good for leaks - they will only spot major leaks
over short time.
The fast MM memory manager that comes with D2006/D2007 has several debug
options - esp. for leaks. Check up on these options for spotting real
leaks - you can use the full debug mode of fastMM to spot lots of
things.
What it does not give you is resource leaks (e.g. handles etc). This
really requires another tool e.g. Automated QA stuff, or using something
like process explorer and a lot of knowledge about how your program
really works.
Myles.
-----Original Message-----
From: delphi-bounces at delphi.org.nz [mailto:delphi-bounces at delphi.org.nz]
On Behalf Of John Bird
Sent: Thursday, 28 June 2007 03:17
To: johnkbird at paradise.net.nz; 'NZ Borland Developers Group - Delphi
List'
Subject: [DUG] Monitoring Memory use
I use Sysinternals Process explorer to monitor the memory that the IDE
and
my programs are using (eg looking for memory leaks etc). (Incidentally
the
D2007 IDE seems much improved in not using memory up over time)
Sysinternals give several different measure of memory use: Working set,
Peak
working set, virtual memory, Page fault etc. I am wondering which is
the
best to track to judge the real impact on Windows and which is the best
to
watch for picking up memory leaks?
John
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject:
unsubscribe
Attention:
This communication is confidential and may be legally privileged. If you are not the intended recipient, please do not use, disclose, copy or distribute it, other than to return it to us with your confirmation that it has been deleted from your system.
More information about the Delphi
mailing list