🚀 go-pugleaf

On Wed, 31 Mar 2004 09:36:17 +0700, Sara T. wrote:

> My software calls simple API i.e. malloc() and free() to allocate and free
> the memory, otherwise I use simple component such as ListBox

Why use malloc()/free()? I doubt it's the cause of the problem but I
thought they were actually deprecated in favour of new/delete? The latter
are certainly easier to use and if you're using objects they are essential.

Your first step should be to use a memory validator such as Code Guard to
confirm that you aren't leaking memory (IOW every call to malloc() as a
matching call to free().

If you know you aren't leaking memory then are you doing a lot of
allocations mixing small/large blocks?

That kind of allocation style seems to prevent the Borland Heap Manager
from tracking free space in the heap. My current theory is that the HM has
a limit on the number of free blocks it will track and eventually it starts
to forget older blocks.

In /theory/ you shouldn't actually need to worry about increasing VM size.
It will eventually be released when your application exits and on most
systems there's plenty of disk space for the page file to grow into but I
don't like seeing it either :)

--
Andrue Cope
[Bicester UK]