From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Robert Cragie" <rcc@jennic.com>
To: <colin.ford@pipinghotnetworks.com>, "Ecos Mailing List" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] goAhead not going ahead...
Date: Mon, 30 Oct 2000 09:26:00 -0000
Message-id: <NDBBLOIOMLKELOJBAPAGCEDECCAA.rcc@jennic.com>
References: <39FDA013.BF42D0E6@pipinghotnetworks.com>
X-SW-Source: 2000-10/msg00374.html

It's a long shot, but it might be heap fragmentation problems. I have
certainly had problems in similar applications using heap allocation with
larg(ish) images. I fixed it using pool memory (i.e. using arrays of
different sized memory chunks). This is wasteful as it typically
overallocates, but there are no fragmentation problems.

Robert Cragie

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [ mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Colin Ford
> Sent: 30 October 2000 16:22
> To: Ecos Mailing List
> Subject: [ECOS] goAhead not going ahead...
>
>
> Hello,
>
> I sent a message earlier about goAhead stopping serving
> pages after a while. Well it seems that its running out of
> memory. Something not being freed?
>
> Anyone got a fix?
> Cheers,
> Col.
>
> --
> ===========================================
> Colin Ford               PipingHot Networks
> Software Engineer        +44 (0)1364 655510
>
>
>