From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:89008] Re: [Ruby trunk Bug#11174] threads memory leak
Date: Fri, 14 Sep 2018 11:09:55 +0000 [thread overview]
Message-ID: <20180914110955.nfjgjjn724ouq2zv@whir> (raw)
In-Reply-To: <redmine.journal-74032.20180914091756.663a4b9cb43b134c@ruby-lang.org>
hartator@gmail.com wrote:
> Issue #11174 has been updated by hartator (Julien Khaleghy).
> Any idea if it's already fixed somewhere else, or you guys
> still working on it?
I missed it, too :x (and now I'm too sleepy to continue...).
It seems specific to glibc (tested 2.24-11+deb9 on Debian
stable) and does not happen with jemalloc (3.6.0).
And it is NOT because of memalign fragmentation, either(*); I
disabled memalign usage to fallback to the aligned malloc+free
fallback; but can still reproduce it.
Finally, it needs multiple threads to reproduce the issue,
a single thread is not enough.
(*) https://sourceware.org/bugzilla/show_bug.cgi?id=14581
next prev parent reply other threads:[~2018-09-14 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11174.20150523211647@ruby-lang.org>
2015-05-23 21:16 ` [ruby-core:69341] [Ruby trunk - Bug #11174] [Open] threads memory leak from-ruby-lang
2015-07-02 15:48 ` [ruby-core:69845] [Ruby trunk - Bug #11174] " from-ruby-lang
2017-08-29 7:41 ` [ruby-core:82499] [Ruby trunk Bug#11174] " kadmos
2017-09-15 2:27 ` [ruby-core:82802] " ko1
2018-09-14 9:17 ` [ruby-core:89004] " hartator
2018-09-14 11:09 ` Eric Wong [this message]
2018-09-14 11:25 ` [ruby-core:89010] " Eric Wong
2019-06-17 15:17 ` [ruby-core:93203] " from-ruby-lang
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180914110955.nfjgjjn724ouq2zv@whir \
--to=ruby-core@ruby-lang.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).