On Tue, 25 Sep 2001, Frank Heckenbach wrote:
Miklos Cserzo wrote:
On Mon, 24 Sep 2001, Martin Liddle wrote:
There certainly was a serious memory leak problem in the run time system that gave us a lot of grief, however it was fixed by Frank in late May so it isn't that one you are seeing. We certainly aren't currently seeing any memory leaks in applications that run for several days at a time. You will need to provide some more information to help in isolating the problem. Can you provide a reasonable size test program that demonstrates the problem?
My code is a bit complex I rather wouldn't post it unless it's unavoidable. All I can say now: there is no dynamic memory allocation involved nor pointers nor anything notoriously easy to make it wrong. Only very basic straight Pascal.
I have similiar (?) problem with GPC version 20010623. It's also platform independant - it appears with versions built for Linux on i386 and Solaris on Sparc. The same code that consumes not more that 5 MB on Solaris/i386 (GPC 20010121) while working now gets more that 30 MB of memory, growing linearly.
There is a known problem. Some operations (esp. string concatenation) need temporary storage (on the stack) which isn't freed immediately, so it will accumulate in loops. A trivial example follows. I think we know the cause of the problem (alloca_string if anyone cares) and therefore can fix it soon.
In my case there is not much string manipulation staff, but a lot of dynamic allocation ... Still I'm very anxious to check whether it can help me when you manage to fix it.
Regards, Adam Naumowicz
-------------------------------------- WWW: http://math.uwb.edu.pl/~adamn/ --------------------------------------