ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "hms (Hal Spitz) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hms (Hal Spitz)" <noreply@ruby-lang.org>
Subject: [ruby-core:119413] [Ruby master Bug#20779] Un-rescuable thread creation limit on Mac
Date: Wed, 02 Oct 2024 23:31:53 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-20779.20241002233153.54270@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20779.20241002233153.54270@ruby-lang.org>

Issue #20779 has been reported by hms (Hal Spitz).

----------------------------------------
Bug #20779: Un-rescuable thread creation limit on Mac
https://bugs.ruby-lang.org/issues/20779

* Author: hms (Hal Spitz)
* Status: Open
* ruby -v: 3.3.5
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
Thread.new will hang the ruby process once past the OSX limit.  It does not appear that's possible to trap and rescue failed thread creation.

It seems the Mac has a limit to the number of threads it supports and googling the issue suggests the limit has been known to change with hardware and OS releases. While I hit the thread creation limit due to a bug in my code and the number of threads that I was attempting to create (12,250+) is an unlikely use-case, I am hoping it would be possible to turn this into a rescuable error.

While I'm reporting this on 3.3.5, I have tested the issue and the inability to rescue back to 3.3.1.

(Thanks to @raels for being a great second set of eyes to make sure I wasn't doing anything goofy / wrong before making this report.  Also, another callout and thanks to both @eregon and @bensheldon over at concurrent-ruby for the unbelievably quick and helpful response to my initial bug report over there).

---Files--------------------------------
hang.rb (713 Bytes)


-- 
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/lists/ruby-core.ml.ruby-lang.org/

       reply	other threads:[~2024-10-02 23:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 23:31 hms (Hal Spitz) via ruby-core [this message]
2024-12-23 18:46 ` [ruby-core:120381] " luke-gru (Luke Gruber) 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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.issue-20779.20241002233153.54270@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@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 NNTP newsgroup(s).