Mail Archives: djgpp/2002/03/13/08:15:35
Giovanni Spagnuolo <spanish AT ieee DOT org> wrote:
> MSG: Listing info about allocated blocks at end(?) of program:
> INFO: 37 blocks currently allocated.
> INFO: 163036428 bytes of memory currently used.
> INFO: 163036428 bytes maximum memory used.
37 currently open allocs using 160 Megs, and over 20000 new[] and
free[] calls up to this point.... to me this looks like you have a
serious algorithmical problem. You'll want to redesign your memory
allocation strategy all the way from the start. E.g. try to avoid
short-term new[]-free[] pairs for temporary variables whenever
possible. C++ operator overloads can cause lots of grief in this area
--- using them to implement maths on large matrices may not be nearly
as good an idea as it seems, at first glance.
> As you can see, there are no memory bugs, but the maximum available
> memory is about 163MB, while I have 256MB of RAM installed.
That can happen, due to rounding of memory block sizes to the next
power of two. I.e. you "use" more memory than you actually get. And
then there's heap fragmentation that could also be a part of the
problem.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -