* [ruby-core:92628] [Ruby trunk Bug#15844] VM has trouble releasing memory (?)` on NoMethodError
[not found] <redmine.issue-15844.20190512202653@ruby-lang.org>
@ 2019-05-12 20:26 ` alangano
2019-05-13 23:50 ` [ruby-core:92636] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) " nobu
2019-05-14 5:41 ` [ruby-core:92641] " duerst
2 siblings, 0 replies; 3+ messages in thread
From: alangano @ 2019-05-12 20:26 UTC (permalink / raw)
To: ruby-core
Issue #15844 has been reported by alangano (Alan Gano).
----------------------------------------
Bug #15844: VM has trouble releasing memory (?)` on NoMethodError
https://bugs.ruby-lang.org/issues/15844
* Author: alangano (Alan Gano)
* Status: Open
* 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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:92636] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) on NoMethodError
[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
2019-05-14 5:41 ` [ruby-core:92641] " duerst
2 siblings, 0 replies; 3+ messages in thread
From: nobu @ 2019-05-13 23:50 UTC (permalink / raw)
To: ruby-core
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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:92641] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) on NoMethodError
[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 ` [ruby-core:92636] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) " nobu
@ 2019-05-14 5:41 ` duerst
2 siblings, 0 replies; 3+ messages in thread
From: duerst @ 2019-05-14 5:41 UTC (permalink / raw)
To: ruby-core
Issue #15844 has been updated by duerst (Martin Dürst).
nobu (Nobuyoshi Nakada) wrote:
> 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.
Recursion should not be a problem. Cycles definitely will be a problem.
> Define your own `inspect` method not to include `@left` and `@right` members.
This is definitely the right way to go. But would it make sense to wrap the error output in a timeout, to make it easier to debug such problems in the field? I can create a feature for this.
----------------------------------------
Bug #15844: VM has trouble releasing memory (?) on NoMethodError
https://bugs.ruby-lang.org/issues/15844#change-78004
* 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/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-05-14 5:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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 ` [ruby-core:92636] [Ruby trunk Bug#15844] VM has trouble releasing memory (?) " nobu
2019-05-14 5:41 ` [ruby-core:92641] " duerst
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).