You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Stefan Eissing <st...@greenbytes.de> on 2017/02/01 05:36:37 UTC

Re: mod_http2 and Frequent wake-ups for mpm_event

Stefan,

did not have the time to look at it really. Will do, but very busy right now. 

> Am 31.01.2017 um 16:01 schrieb Stefan Priebe - Profihost AG <s....@profihost.ag>:
> 
> Hi Yann,
>  Hi Stefan,
> 
> any ideas?
> 
> Stefan
> 
>> Am 27.01.2017 um 20:30 schrieb Ruediger Pluem:
>> 
>> 
>>> On 01/27/2017 08:10 PM, Stefan Priebe - Profihost AG wrote:
>>> Hi Yann,
>>> 
>>> this is now a segfault with mod_http2 + beam v4 patch + mpm v7 patch:
>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>> #0  allocator_free (node=0x0, allocator=0x7f8974080c90)
>>>    at memory/unix/apr_pools.c:381
>>> #0  allocator_free (node=0x0, allocator=0x7f8974080c90)
>>>    at memory/unix/apr_pools.c:381
>>> #1  apr_pool_clear (pool=0x7f89740830d8) at memory/unix/apr_pools.c:793
>> 
>> pool from above != pool_to_recycle from below is strange.
>> 
>>> #2  0x00005611421447a8 in ap_push_pool (queue_info=0x0,
>> 
>> queue_info NULL? That looks bad.
>> 
>>>    pool_to_recycle=0x7f8974080c98) at fdqueue.c:234
>>> #3  0x000056114213faea in process_lingering_close (cs=0x7f8974083368,
>>>    pfd=0x561142cc97f8) at event.c:1513
>>> #4  0x0000561142143620 in listener_thread (thd=0x0, dummy=0x54716c3684bbc)
>>>    at event.c:1837
>>> #5  0x00007f8989bb20a4 in start_thread ()
>>>   from /lib/x86_64-linux-gnu/libpthread.so.0
>>> #6  0x00007f89898e762d in clone () from /lib/x86_64-linux-gnu/libc.so.6
>> 
>> Regards
>> 
>> Rüdiger
>>

Re: mod_http2 and Frequent wake-ups for mpm_event

Posted by Stefan Priebe <s....@profihost.ag>.
Am 01.02.2017 um 06:36 schrieb Stefan Eissing:
> Stefan,
>
> did not have the time to look at it really. Will do, but very busy right now.

Thanks - no problem.

>
>> Am 31.01.2017 um 16:01 schrieb Stefan Priebe - Profihost AG <s....@profihost.ag>:
>>
>> Hi Yann,
>>  Hi Stefan,
>>
>> any ideas?
>>
>> Stefan
>>
>>> Am 27.01.2017 um 20:30 schrieb Ruediger Pluem:
>>>
>>>
>>>> On 01/27/2017 08:10 PM, Stefan Priebe - Profihost AG wrote:
>>>> Hi Yann,
>>>>
>>>> this is now a segfault with mod_http2 + beam v4 patch + mpm v7 patch:
>>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>>> #0  allocator_free (node=0x0, allocator=0x7f8974080c90)
>>>>    at memory/unix/apr_pools.c:381
>>>> #0  allocator_free (node=0x0, allocator=0x7f8974080c90)
>>>>    at memory/unix/apr_pools.c:381
>>>> #1  apr_pool_clear (pool=0x7f89740830d8) at memory/unix/apr_pools.c:793
>>>
>>> pool from above != pool_to_recycle from below is strange.
>>>
>>>> #2  0x00005611421447a8 in ap_push_pool (queue_info=0x0,
>>>
>>> queue_info NULL? That looks bad.
>>>
>>>>    pool_to_recycle=0x7f8974080c98) at fdqueue.c:234
>>>> #3  0x000056114213faea in process_lingering_close (cs=0x7f8974083368,
>>>>    pfd=0x561142cc97f8) at event.c:1513
>>>> #4  0x0000561142143620 in listener_thread (thd=0x0, dummy=0x54716c3684bbc)
>>>>    at event.c:1837
>>>> #5  0x00007f8989bb20a4 in start_thread ()
>>>>   from /lib/x86_64-linux-gnu/libpthread.so.0
>>>> #6  0x00007f89898e762d in clone () from /lib/x86_64-linux-gnu/libc.so.6
>>>
>>> Regards
>>>
>>> R�diger
>>>
>