On Tue, Jul 12, 2016 at 10:05:35AM -0700, Will Yardley wrote:
> Has any recent work been done on adding Kyoto Cabinet support for mutt,
> since it looks like Tokyo Cabinet has been deprecated by its creators in
> favor of Kyoto Cabinet?
>
> I see this patch from a while back:
> https://gist.github
On Tue, Jul 12, 2016 at 01:44:33PM -0500, Will Fiveash wrote:
> Today I did some memory leak testing of mutt v1.6.2 and found that when
> sending email via mutt->libsasl->libcrypto (OpenSSL) there were a number
> of memory leaks. Basically I see about 10KB leaked per message sent.
> Has anyone els
changeset: 6724:488f91a85115
user: Kevin McCarthy
date: Tue Jul 12 18:04:28 2016 -0700
link: http://dev.mutt.org/hg/mutt/rev/488f91a85115
Fix BODY->d_filename memory leaks.
mutt_message_to_7bit() and transform_to_7bit() were overwriting
d_filename without freeing the previous valu
changeset: 6723:b4de6941bbb9
user: Kevin McCarthy
date: Tue Jul 12 17:46:09 2016 -0700
link: http://dev.mutt.org/hg/mutt/rev/b4de6941bbb9
Fix BODY->charset memory leaks.
mutt_get_content_info() was directly setting charset without freeing the
previous value.
mutt_free_body() was
Today I did some memory leak testing of mutt v1.6.2 and found that when
sending email via mutt->libsasl->libcrypto (OpenSSL) there were a number
of memory leaks. Basically I see about 10KB leaked per message sent.
Has anyone else observed this?
Note that my configuration is using smtp_url="smtps:
Has any recent work been done on adding Kyoto Cabinet support for mutt,
since it looks like Tokyo Cabinet has been deprecated by its creators in
favor of Kyoto Cabinet?
I see this patch from a while back:
https://gist.github.com/aeroevan/9508433
though I assume it wouldn't apply to 1.6.
I also r
