Red Hat Bugzilla – Bug 216776
Avoid memory leaks
Last modified: 2007-11-30 17:07:37 EST
The stable upstream version 2.2.98 has a few memory leak fixes, that we should
probably pull in:
* libsoup/soup-message-client-io.c (parse_response_headers): Avoid
memory leak when parse_response_headers() is called on a message
that has a 'reason_phrase' already for some reason.
* libsoup/soup-gnutls.c (soup_gnutls_free): Avoid memory leak:
hostname was not freed.
(soup_ssl_wrap_iochannel): Avoid memory leak: SoupGNUTLSChannel
'chan' was not freed in case of initialization error. Avoid double
close of the "real" (plain, non-ssl) channel FD.
* libsoup/soup-socket.c (soup_socket_start_proxy_ssl): Avoid
memory leak: the "real" (plain, non-ssl) GIOChannel was never
"finally" unreffed (one more *_ref() than *_unref()) in case of
Should we backport the individual memory leak fixes or just upgrade to 2.2.98?
Answering my own question...
Fixed in libsoup-2.2.98-1.el5.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.