From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92636] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) on NoMethodError
Date: Mon, 13 May 2019 23:50:06 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-77997.20190513235005.9d577fb62cac2ac9@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15844.20190512202653@ruby-lang.org
Issue #15844 has been updated by nobu (Nobuyoshi Nakada).
Status changed from Open to Rejected
On exiting by an exception, ruby tries to print the exception and `NoMethodError` shows its receiver.
Your `Node` is a recursive construction, so it increases exponentially by the size.
Define your own `inspect` method not to include `@left` and `@right` members.
----------------------------------------
Bug #15844: VM has trouble releasing memory (?) on NoMethodError
https://bugs.ruby-lang.org/issues/15844#change-77997
* Author: alangano (Alan Gano)
* Status: Rejected
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
When the test case is run, the process goes haywire. I observe RSS bouncing around, and trending upwards. CPU on the process is at 100%.
The test case is a partial implementation of a binary tree which is also a doubly linked list. I chopped it down as far as I could.
The issue is triggered by a calling a non-existent method on the Tree object. The test case only has 100 nodes -- it should be instantaneous. I kill it after some 6+ minutes with RSS hitting upwards of 5GB.
I am working in 2.6.3. Duplicated in 2.5.3 and 2.4.3 (with some code modifications)
---Files--------------------------------
issue.rb (2.67 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-05-13 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15844.20190512202653@ruby-lang.org>
2019-05-12 20:26 ` [ruby-core:92628] [Ruby trunk Bug#15844] VM has trouble releasing memory (?)` on NoMethodError alangano
2019-05-13 23:50 ` nobu [this message]
2019-05-14 5:41 ` [ruby-core:92641] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) " duerst
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-77997.20190513235005.9d577fb62cac2ac9@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).