From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Encode.pm leak in v2.87..v3.12
Date: Tue, 12 Oct 2021 10:59:40 +0000 [thread overview]
Message-ID: <20211012105940.GA19169@dcvr> (raw)
In-Reply-To: <20211005112531.13664-1@dcvr>
Eric Wong <e@80x24.org> wrote:
> The leak's been there for a while, but I couldn't find
> other reports of it:
>
> https://rt.cpan.org/Public/Bug/Display.html?id=139622
So this got fixed in Encode 3.13, and 3.15 (3.14 segfaulted :P).
Perl v5.36 will have 3.15 (or possibly a newer version). This
has been a leak since 2016 (2.87), so there might be lot of
people affected...
CentOS 7.x has Encode 2.51 so it's probably not affected by
this particular bug...
> In the meantime, I may need to put in my own workaround for it
> PublicInbox::Eml because distros are slow moving...
It's tracked for Debian, at least https://bugs.debian.org/995804
Our "eval { $eml->body_str }" usage is kinda dumb, so maybe it
could be done better w/o needing eval at all...
next prev parent reply other threads:[~2021-10-12 10:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 23:53 httpd memory usage? Eric Wong
2021-09-27 7:10 ` Eric Wong
2021-10-04 0:07 ` [PATCH 0/2] www: fix ref cycles when threading extindex Eric Wong
2021-10-04 0:07 ` [PATCH 1/2] t/thread-cycle: make Email::Simple optional Eric Wong
2021-10-04 0:07 ` [PATCH 2/2] www: fix ref cycle from threading w/ extindex Eric Wong
2021-10-04 22:51 ` [PATCH 0/2] www: fix ref cycles when threading extindex Eric Wong
2021-10-05 11:33 ` Encode.pm leak Eric Wong
2021-10-12 10:59 ` Eric Wong [this message]
2021-10-13 10:16 ` [PATCH 0/7] workaround Encode leak, several test fixes Eric Wong
2021-10-13 10:16 ` [PATCH 1/7] xt/perf-msgview: drop unnecessary use_ok Eric Wong
2021-10-13 10:16 ` [PATCH 2/7] test_common: hoist out tail_f sub Eric Wong
2021-10-13 10:16 ` [PATCH 3/7] t/www_listing: require opt-in for grokmirror tests Eric Wong
2021-10-13 10:16 ` [PATCH 4/7] eml: avoid Encode 2.87..3.12 leak Eric Wong
2021-10-13 10:16 ` [PATCH 5/7] t/lei-mirror: avoid reading ~/.public-inbox/config in test Eric Wong
2021-10-13 10:16 ` [PATCH 6/7] t/git: avoid "once" warning for async_warn Eric Wong
2021-10-13 10:16 ` [PATCH 7/7] t/nntpd-tls: change diag() to like() assertion Eric Wong
2021-11-04 0:17 ` httpd memory usage? Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211012105940.GA19169@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).