https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
--- Comment #6 from Christophe JAILLET ---
For the records, it has been backported in the 2.4.x branch in r1875552.
This is part of 2.4.43.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
Giovanni Bechis changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
--- Comment #4 from Giovanni Bechis ---
This makes sense for me.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
Craig changed:
What|Removed |Added
CC||candr...@integralblue.com
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
Christophe JAILLET changed:
What|Removed |Added
Keywords||PatchAvailable
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
--- Comment #3 from paolo ---
Created attachment 36498
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36498=edit
Proposed patch
Hi,
I could fix this leak by adding those lines in ssl_util_stapling.c
static int stapling_cb(SSL *ssl,
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
--- Comment #2 from paolo ---
Hi,
any news on this leak. Could you reproduce the issue?
Many thanks for your answer.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63077
--- Comment #1 from paolo ---
Here the stacktrace of the leak:
==10180== 3,720 (32 direct, 3,688 indirect) bytes in 2 blocks are definitely
lost in loss record 207 of 247
==10180==at 0x4C29BC3: malloc (vg_replace_malloc.c:299)
==10180==
