Backported. Will also release v1.10.6 on github shortly.
> Am 06.06.2017 um 10:53 schrieb Stefan Eissing <stefan.eiss...@greenbytes.de>:
>
>>
>> Am 06.06.2017 um 10:45 schrieb Plüm, Rüdiger, Vodafone Group
>> <ruediger.pl...@vodafone.com>:
>>
>>
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de]
>>> Gesendet: Dienstag, 6. Juni 2017 10:40
>>> An: dev@httpd.apache.org
>>> Betreff: Re: The drive for 2.4.26
>>>
>>> Proposed the patch as fix, since we did not see the behaviour pop up
>>> again over the last days at Steffen's system.
>>>
>>> I assume the RTC is in place now.
>>
>> My personal opinion: Only after 2.4.26 is released. So from my personal
>> point of view you can go ahead backporting.
>> Others may see this differently.
>
> I shall use the time our US friends are still slumbering on to back port the
> change, taking your statement as an excuse. :-P
>
> -Stefan
>
>>
>> Regards
>>
>> Rüdiger
>>
>>>
>>> -Stefan
>>>
>>>> Am 06.06.2017 um 09:26 schrieb Stefan Eissing
>>> <stefan.eiss...@greenbytes.de>:
>>>>
>>>> I made a patch on Friday evening for Steffen's system where the
>>> behaviour happens. Hope to hear back from him today.
>>>>
>>>> -Stefan
>>>>
>>>>> Am 06.06.2017 um 03:12 schrieb Eric Covener <cove...@gmail.com>:
>>>>>
>>>>> On Tue, May 30, 2017 at 9:12 AM, Stefan Eissing
>>>>> <stefan.eiss...@greenbytes.de> wrote:
>>>>>> I have one report of a CPU busy loop that seems to only happen on
>>> the last 3 changes in mod_http2. Steffen is currently testing if a
>>> feature disable solves the problem and thus points to the cause. I hope
>>> to hear from him tomorrow sometime during the day if that addresses the
>>> issue or not.
>>>>>>
>>>>>> Otherwise I am hesitant to make any more changes from my side and
>>> hope we can go forward with a release.
>>>>>
>>>>>
>>>>> Anything on this?
>>>>>
>>>>> --
>>>>> Eric Covener
>>>>> cove...@gmail.com
