This was indeed a fakewap specific thing: leak appears when there are no headers.
But even when stress testing pure wap, you probably want to add headers sending
to fakewap, so this leak is not important.


aarno

On 12.11.2003, at 13:54, Aarno Syv�nen wrote:

All help welcome ;

But this one walks like a leak and talks like a leak: I ran fakewap + wapbox
and after 6080 transactions there was PANIC: too many concurrent allocations.
This of course may be caused by fakewap activating some very specific
branches.


Aarno

On 12.11.2003, at 13:45, Stipe Tolj wrote:

Aarno Syv�nen wrote:

There is a memory leak in wapbox. Configuring --with-defaults=speed should result with longer uptime.

Meanwhile, I started to investigate.

Aarno, check my bug updates in Mantis. There are some PANICs caused by HTTP headers that come with a single space " " character as value.

I'm after this and will fix in a couple of minutes.

Stipe

mailto:[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG

M�nsterstr. 248
40470 D�sseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:[EMAIL PROTECTED]
http://www.wapme-systems.de/
-------------------------------------------------------------------

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.2 (Cygwin)

mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-----END PGP PUBLIC KEY BLOCK-----







Reply via email to