ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: usa@garbagecollect.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71266] [Ruby trunk - Bug #11613] test_aspawn_too_long_path creates too many processes
Date: Thu, 29 Oct 2015 14:28:22 +0000	[thread overview]
Message-ID: <redmine.journal-54639.20151029142822.e168631798ee6186@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11613.20151022165233@ruby-lang.org

Issue #11613 has been updated by Usaku NAKAMURA.

Backport changed from 2.0.0: REQUIRED, 2.1: REQUIRED, 2.2: REQUIRED to 2.0.0: REQUIRED, 2.1: DONE, 2.2: REQUIRED

ruby_2_1 r52358 merged revision(s) 52229,52273,52277,52357.

----------------------------------------
Bug #11613: test_aspawn_too_long_path creates too many processes
https://bugs.ruby-lang.org/issues/11613#change-54639

* Author: Yui NARUSE
* Status: Closed
* Priority: Normal
* Assignee: 
* ruby -v: 
* Backport: 2.0.0: REQUIRED, 2.1: DONE, 2.2: REQUIRED
----------------------------------------
At least on FreeBSD, spawn("echo|echo|echo|echo|echo|echo|echo| ...20000 times") success and create 20000 zombie processes.
To prevent this you can add rlimit_nproc: 1 because it tests sh itself, don't test spawned echos.

```diff
diff --git a/test/ruby/test_process.rb b/test/ruby/test_process.rb
index 32dcaed..7877171 100644
--- a/test/ruby/test_process.rb
+++ b/test/ruby/test_process.rb
@@ -1600,7 +1600,7 @@ class TestProcess < Test::Unit::TestCase
       assert_raise(*exs, mesg) do
         begin
           loop do
-            Process.spawn(cmds.join(sep), [STDOUT, STDERR]=>File::NULL)
+            Process.spawn(cmds.join(sep), [STDOUT, STDERR]=>File::NULL, rlimit_nproc: 1)
             min = [cmds.size, min].max
             cmds *= 100
           end
```



-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2015-10-29 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11613.20151022165233@ruby-lang.org>
2015-10-22 16:52 ` [ruby-core:71161] [Ruby trunk - Bug #11613] [Open] test_aspawn_too_long_path creates too many processes naruse
2015-10-22 16:54 ` [ruby-core:71162] [Ruby trunk - Bug #11613] " naruse
2015-10-29 14:28 ` usa [this message]
2015-11-28 18:30 ` [ruby-core:71724] " nagachika00

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-54639.20151029142822.e168631798ee6186@ruby-lang.org \
    --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).