On Mon, 8 Apr 2002, Greg Ames wrote: > hmmm, I wonder what changed since 2.0.32 to trigger the failure then? > Maybe it's some of the internal_fast_redirect stuff, which affects this > URL.
Could be. It's most likely some combination of setaside being called and then a brigade being cleaned up without all of the buckets being emptied from it before-hand. If the internal_fast_redirect stuff could cause that (I suppose it possibly could), then.... > > Greg, can you try this patch on daedalus for me? > > Sure, no problem. But it will probably be a while before it goes live. > Last time I checked we had 415 active requests, and we've hit 600 > (ServerLimit) today. Mondays typically are heavy load days, plus I > think we're getting /.ed . 'kay. In the meanwhile I'll try to pin down an exact request that will cause it to segfault. -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
