https://bz.apache.org/bugzilla/show_bug.cgi?id=56984
--- Comment #8 from [email protected] --- There is now activity going on in the php5 Apache2 handler to solve the segfaults with pipelined client requests by not relying anymore on the destruction of the request pool between two client requests on the same connection. However there is some confusion about when the pool destructions are eventually going to run. It seems that disconnection is the only signal for a prefork worker to process the EOR buckets. Responses are fully sent earlier but not the EOR bucket. What if the client indicated keep-alive? In this situation, module programmers will have to think hard about what they are allocating in the pool. There will be lots of modules that rely on cleanup callbacks to run after each client request gets processed, and a module programmer cannot influence the amount of requests sent on one connection by the client or for how long it stays connected. It seems that doing your own memory management is the only option going forward for anything that exceeds a couple of kilobytes. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
