On 25 Nov 2011, at 08:43, Marco van de Voort wrote:
IMHO if you get into trouble with this, you are already walking on
the edge
of the abyss. Using cmem (or any other advanced memory manager)
might give
short time relieve because it probably has a different allocation
pattern.
Not necess
In our previous episode, Jonas Maebe said:
> I've never seen any reports of heaptrc failing to report memory leaks.
> Most likely, your problems stem from internal heap fragmentation
> rather than from memory leaks. Such problems can usually be solved by
> using the "cmem" unit, which falls b
On: Thu, 24 Nov 2011 17:06:18 +0100 Jonas Maebe
wrote
> On 24 Nov 2011, at 16:28,
> > wrote:
> > ...
> > only odd thing was that TotalAllocated sometimes came back negative in
> > the threads as the program approached the point of running out of
> > memory
>
> The fact that the heap
On 24 Nov 2011, at 16:28, > wrote:
At no point did the heap status reveal the growing amount of space
tied up: the
only odd thing was that TotalAllocated sometimes came back negative in
the threads as the program approached the point of running out of
memory
(at the 2GB addressing limit;
A recent query:
Date: Mon, 21 Nov 2011 08:27:16 + From: Mark Morgan Lloyd
Subject: [fpc-pascal] Debugging ancient
heap allocation
seems not to have received a reply. The problem of debugging
memory allocation, however, is wider and not just involving
ancient code!
I am using:
Compiler 2.4
