From: "matz (Yukihiro Matsumoto)" <matz@...>
Date: 2012-07-14T17:46:31+09:00
Subject: [ruby-core:46439] [ruby-trunk - Bug #6291][Closed] Backtrace printout halts for an extremely long time when large amounts of data are allocated


Issue #6291 has been updated by matz (Yukihiro Matsumoto).

Status changed from Assigned to Closed

This one is not easy to fix.
We try to address it by improving #inspect, but we cannot make promise.

Matz.

----------------------------------------
Bug #6291: Backtrace printout halts for an extremely long time when large amounts of data are allocated
https://bugs.ruby-lang.org/issues/6291#change-28063

Author: cuthbert (Christoffer Lervag)
Status: Closed
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 1.9.3
ruby -v: 1.9.3


=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



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