From: John Mills <johnmills@speakeasy.net>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Memory leakage problem with GoAhead web server
Date: Wed, 06 Jun 2007 16:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0706060903120.27736-100000@otter.localdomain> (raw)
All -
I'm working on an embedded eCos/MIPS32/OpenSSL product which I recently
converted from eCos' basic 'httpd' to the free version of the 'GoAhead'
server. Now I experience memory leakage.
I test with a simple script that repeatedly invokes 'wget' to request the
default index page over an 'https' link, and find the web server gradually
claiming more and more dynamic memory - until the server finally fails to
accept new connections.
If other users have encountered this problem or could suggest ways to
narrow the diagnosis, I would really appreciate hearing about it.
TIA.
- John Mills
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-06-06 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 16:07 John Mills [this message]
2007-06-06 16:24 ` Gary Thomas
2007-06-06 19:03 ` John Mills
2007-06-07 3:16 ` Andrew Lunn
2007-06-07 4:08 ` John Mills
2007-06-07 4:43 ` [ECOS] " Grant Edwards
2007-06-07 8:49 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0706060903120.27736-100000@otter.localdomain \
--to=johnmills@speakeasy.net \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john.m.mills@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).