Project

General

Profile

Actions

Bug #6291

closed

Backtrace printout halts for an extremely long time when large amounts of data are allocated

Added by cuthbert (Christoffer Lervag) about 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Target version:
ruby -v:
1.9.3
Backport:
[ruby-core:44346]

Description

=begin
When large amounts of data are allocated, it can take an eternity for the backtrace printout to complete. Here's a simple example:

class SomeClass
  def initialize
    @a = Array.new(100000, "just some random string")
  end
end
h = Hash.new
200.times {|i| h[i] = SomeClass.new}
h.asdf

This will halt with the following printout:
test.rb:9

And then, after a very long time (depending on how much data is in memory), it will eventually finish:
test.rb:9: undefined method `asdf' for #Hash:0x1001bc348 (NoMethodError)

For me, this has caused a lot of frustration when running a test suite on an application which loads a lot of data in memory, as in many cases I will never get to see the actual backtrace. This makes debugging much more difficult. Perhaps there is some fundamental property of the Ruby language itself that makes this an 'expected behaviour', but if not, I would really appreciate to see this adressed.
=end


Related issues 2 (2 open0 closed)

Related to Ruby master - Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to callOpenActions
Has duplicate Ruby master - Feature #6783: Infinite loop in inspect, not overriding inspect, to_s, and no known circular references. Stepping into inspect in debugger locks it up with 100% CPU.OpenActions
Actions

Also available in: Atom PDF