> Am 09.05.2019 um 11:28 schrieb Yann Ylavic <[email protected]>:
>
> No it's not actually, nevermind.
Yeah, I was going back and forth like that myself. Therefore my question. ;)
I am seeing in an uncomitted change a rare occasion where eor_bucket_destroy()
seems to destroy a pool twice. If that is related to a bucket copy, I have not
found out yet. But it's one more peculiarity to keep in mind...
Thanks, guys!
> On Thu, May 9, 2019 at 11:24 AM Yann Ylavic <[email protected]> wrote:
>>
>> Hmm, if r->pool gets destroyed by the first eor, the
>> eor_bucket_cleanup() for the copy should NULLify its b->data at the
>> same time, so it should be safe no?
>>
>> On Thu, May 9, 2019 at 11:22 AM Plüm, Rüdiger, Vodafone Group
>> <[email protected]> wrote:
>>>
>>> I think your understanding is correct.
>>>
>>> Regards
>>>
>>> Rüdiger
>>>
>>>
>>> C2 General
>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Stefan Eissing <[email protected]>
>>>> Gesendet: Donnerstag, 9. Mai 2019 11:02
>>>> An: [email protected]
>>>> Betreff: eor bucket
>>>>
>>>> Could someone help me to check my understanding of the eor bucket
>>>> implementation?
>>>>
>>>> If an eor bucket is ever copied, there are 2 buckets with their b->data
>>>> pointing to the request_rec. Since this is local to the bucket,
>>>> destroying these 2 will call apr_pool_destroy() twice on the pool.
>>>> Correct?
>>>>
>>>> -Stefan
