On Jan 18, Doug MacEachern wrote:
> On Tue, 11 Jan 2000, Jim Winstead wrote:
> > There appears to be a file upload bug in libapreq that causes httpd
> > processes to spin out of control. There's a mention of this in the
> > mailing list archives with a patch that seems to be a partial
> > solution, but we're still seeing problems even with the patch I've
> > attached. They appear to get stuck in the strstr() call.
> >
> > Anyone tracked this one down before? We haven't had any real luck
> > figuring out what triggers the condition that sends things into a
> > tail-spin, and I admittedly haven't crawled through the code too
> > carefully to see what could be going wrong.
>
> do you have a test case I can use to reproduce the strstr() hang bug?
Not yet. We've seen it on production servers sporadically, but have
not had the time to be able to take the time to properly debug it
at all. (Since the simple tests I've tried have failed, I suspect
it may be do to slow clients timing out their requests or some
interaction with the front-end server when that happens.)
I also saw the huge-memory-bloat issue that someone else reported
recently with uploading a large file in a test environment (actually,
uploading three files that were each around 10 megs). I'll be
looking into that to see if I can't see where all that memory is
being allocated, since I can actually reproduce that easily. It
wouldn't surprise me if I'm just being dumb in how the file is
getting copied to its final location.
Jim
