ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "ioquatix (Samuel Williams) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "ioquatix (Samuel Williams)" <noreply@ruby-lang.org>
Subject: [ruby-core:116208] [Ruby master Bug#20184] Ruby segfaults on Fly.io with 256 MB RAM
Date: Sun, 14 Jan 2024 22:09:03 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-106228.20240114220903.53158@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20184.20240114130908.53158@ruby-lang.org

Issue #20184 has been updated by ioquatix (Samuel Williams).


I was also investigating this issue.

On low-memory systems (< ~400MB RAM+Swap), `Init_default_shapes` will fail and cause Ruby to segfault later.

Even something as simple as ruby -e "puts 123" will fail.

The 2nd `mmap` in `shape.c` tries to allocate 384MB as a cache. This fails with `MAP_FAILED` which is stored into a `shape_cache` pointer and later this pointer is derefenced causing a segfault.

The current merged fix skips the cache if the `mmap` fails, but might I suggest we explore the following:

- Divide and conquer strategy for finding an allocation size that works (e.g. divide by half and try again a few times).
- Expose an environment variable to control the size, so that those on memory constrained systems can at least enable a smaller cache.


----------------------------------------
Bug #20184: Ruby segfaults on Fly.io with 256 MB RAM
https://bugs.ruby-lang.org/issues/20184#change-106228

* Author: aalin (Andreas Alin)
* Status: Closed
* Priority: Normal
* ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux]
* Backport: 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: REQUIRED
----------------------------------------
I've been running a Ruby 3.2 app on Fly.io with 256 MB RAM and it has been working fine.
When I upgraded to Ruby 3.3.0, any Ruby script would crash immediately with a segfault.

I haven't been able to reproduce it outside of fly.io.

I created a repository with a basic rack app which crashes on fly.io.
The readme includes the full output and a GDB backtrace.
https://github.com/aalin/ruby-3-3-0-fly-crash



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/

  parent reply	other threads:[~2024-01-14 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 13:09 [ruby-core:116201] [Ruby master Bug#20184] Ruby segfaults on Fly.io with 256 MB RAM aalin (Andreas Alin) via ruby-core
2024-01-14 15:07 ` [ruby-core:116202] " nobu (Nobuyoshi Nakada) via ruby-core
2024-01-14 15:20 ` [ruby-core:116204] " nobu (Nobuyoshi Nakada) via ruby-core
2024-01-14 22:09 ` ioquatix (Samuel Williams) via ruby-core [this message]
2024-01-14 22:10 ` [ruby-core:116209] " ioquatix (Samuel Williams) via ruby-core
2024-02-08  8:19 ` [ruby-core:116626] " anton-stepanof (Anton Stepanov) via ruby-core
2024-03-20 23:27 ` [ruby-core:117272] " naruse (Yui NARUSE) via ruby-core

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=redmine.journal-106228.20240114220903.53158@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.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).