Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
memory-leak fix for 7.88.1
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-distros <curl-distros_at_lists.haxx.se>
Date: Tue, 15 Jul 2025 08:43:31 +0200 (CEST)
Hi curl distro maintainers,
(I know Debian ships this version so I address them specifically here, but I
suspect a few others might as well.)
I have researched and reproduced a memory-leak reported against libcurl 7.88.1
[1] that does not reproduce against modern versions.
In the curl issue there is a valid fix [2], that I have tested and vetted. As
curl upstream mainainer, I deem this as the most sensible and least risky fix
to address the issue.
The patch is also made as a git patch and attached to this email.
This patch is sent to you with permission from the original author. (Even if
copyright on a single-line change might be debatable.)
The problem was never specifically detected and fixed in upstream curl. The
chunked handling has however been refactored since 7.88.1 so along the way the
leak was fixed inadvertadly. This is relevant only because it explains why
there is no upstream newer commit available to backport to 7.88.1 to fix this.
Thanks for considering.
[1] = https://github.com/curl/curl/issues/17749
[2] = https://github.com/curl/curl/issues/17749#issuecomment-3007138215
Received on 2025-07-15
Date: Tue, 15 Jul 2025 08:43:31 +0200 (CEST)
Hi curl distro maintainers,
(I know Debian ships this version so I address them specifically here, but I
suspect a few others might as well.)
I have researched and reproduced a memory-leak reported against libcurl 7.88.1
[1] that does not reproduce against modern versions.
In the curl issue there is a valid fix [2], that I have tested and vetted. As
curl upstream mainainer, I deem this as the most sensible and least risky fix
to address the issue.
The patch is also made as a git patch and attached to this email.
This patch is sent to you with permission from the original author. (Even if
copyright on a single-line change might be debatable.)
The problem was never specifically detected and fixed in upstream curl. The
chunked handling has however been refactored since 7.88.1 so along the way the
leak was fixed inadvertadly. This is relevant only because it explains why
there is no upstream newer commit available to backport to 7.88.1 to fix this.
Thanks for considering.
[1] = https://github.com/curl/curl/issues/17749
[2] = https://github.com/curl/curl/issues/17749#issuecomment-3007138215
-- / daniel.haxx.se || https://rock-solid.curl.dev
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-distros Etiquette: https://curl.se/mail/etiquette.html
- text/x-diff attachment: 0001-http_chunks-reset-the-trailer-to-avoid-memory-leak.patch