FYI: /trunk no longer works with mod_http2. 2.4.x does. I see missing response data, it seems, so the most likely cause are the changes in filter handling. Did not find the time to investigate further.
Please be aware the mod_h2 uses pool/brigade hierarchies in new and unexpected ways. The request has been processed and EOR bucket has been handled in another thread, however data/file handles might have been transferred to the main thread and are being cleaned up when the main connection thinks a stream is done. If those data gets set aside, the memory might get freed/reused too early. Maybe mod_http2 needs to come up with its own EOR buckets on the main connection to allow for cleanup synchronization. Not sure... //Stefan > Am 06.10.2015 um 13:18 schrieb Graham Leggett <[email protected]>: > > On 06 Oct 2015, at 12:36 PM, Graham Leggett <[email protected]> wrote: > >>> How can you be sure that you don't have transient buckets in the brigade >>> that point to memory that changed or is invalid, once you reinstate the >>> brigade? >> >> Because it’s a request filter, not a connection filter. Request filters set >> aside brigades all the time in their local contexts, this is normal. > > I see what you mean - transient buckets specifically will need to be setaside > before the loop ends. Will take a look. > > Regards, > Graham > — > <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
