On Wed, 14 Nov 2001, Ryan Bloom wrote: > Essentially, what is happening, is that we register a cleanup on the > connection pool to call lingering_close. We have a sub-pool from the > connection pool in the core_output_filter. The bug happens anytime we > have not written all of the data when we call lingering_close. Because > we clear all sub-pools before calling the cleanups, we end up calling > into the core_output_filter, looking for a sub-pool that doesn't exist > anymore.
Yeah, that's what I reported two days ago. ;) > I'm still looking for solutions to the bug. There probably needs to be some way for the core_output_filter to know its ctx is no longer valid. Maybe have the core_output_filter register a cleanup on the subpool that will NULL out the ctx->subpool pointer when the subpool goes away? > > telnet localhost 80 > > CONNECT www.google.com HTTP/1.0 FYI, you'll also run into this bug if you have the latest LWP perl package installed when running test #2 of limits.t from the test suite. --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
