Hi Stefan, Apache 2.4.25 + mpm_event V7 and core mod_http2: Core was generated by `/usr/local/apache2/bin/httpd -k start'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000521d98 in h2_stream_out_prepare () (gdb) bt #0 0x0000000000521d98 in h2_stream_out_prepare () #1 0x00007f54f27eba80 in ?? () #2 0x00007f54f27eba8c in ?? () #3 0x00007f54f27eba90 in ?? () #4 0x00007f54ef00e0a0 in ?? () #5 0x00007f54ef00e9a8 in ?? () #6 0x00007f54f27ebac0 in ?? () #7 0x0000000000000000 in ?? ()
so it's crashing with mpm_event and without mpm_event. And it does with core mod_http2 and mod_http2 v1.8.8. Is a regression in mod_http2 possible? Greets, Stefan Am 19.01.2017 um 07:55 schrieb Stefan Priebe - Profihost AG: > Dear Stefan, > dear Yann, > > a longer test run shows it's also crashing without any mpm_event patch > at all. So I'm really sorry. It just starts crashing faster with the > mpm_event patches. > > I'll now retest regarding mod_http2 core, plain apache 2.4.25 and > mod_http v1.8.8 > > may be it's a regression in 2.4.25 itself or in mod_http2. > > Stefan > > Am 19.01.2017 um 00:52 schrieb Yann Ylavic: >> On Wed, Jan 18, 2017 at 10:49 PM, Stefan Priebe - Profihost AG >> <s.pri...@profihost.ag> wrote: >>> >>> v5 does not apply to 2.4.25. If you can send me a v5 version that >>> applies to 2.4.25 i'll test. >> >> Here it is (slightly modified to fix possible deadlocks, per r1762742 >> and r1774538). >> >> Thanks! >>
