ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:89010] Re: [Ruby trunk Bug#11174] threads memory leak
Date: Fri, 14 Sep 2018 11:25:13 +0000	[thread overview]
Message-ID: <20180914112513.ifbkqhfv4or5kxqs@whir> (raw)
In-Reply-To: <20180914110955.nfjgjjn724ouq2zv@whir>

> It seems specific to glibc

That should be "glibc malloc"; and only old versions.  The bug
is fixed in glibc 2.28, at least; likely earlier.  (glibc takes
forever to build) It's present in 2.24-11+deb9 on Debian.

MALLOC_ARENA_MAX=1 MALLOC_ARENA_TEST=1 does not seem to help.

I forgot one other parameter which IS the culprit in older glibc versions:

MALLOC_MMAP_THRESHOLD_=131072  # or whatever fixed value you want

So the sliding mmap threshold was the problem in glibc; but it's
fixed upstream, at least.  Just have to wait for distros to roll
it out...

  reply	other threads:[~2018-09-14 11:25 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   ` [ruby-core:89008] " Eric Wong
2018-09-14 11:25     ` Eric Wong [this message]
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=20180914112513.ifbkqhfv4or5kxqs@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).