Bug #9026: [PATCH] Add ObjectSpace.heap_dump to objspace.so

• Status: Closed
• Assignee: -
• Target version: 2.1.0
• ruby -v: ruby 2.1.0dev (2013-10-16 trunk 43297) [x86_64-darwin12.4.1]
• Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN

[tmm1 (Aman Karmani)]

https://github.com/ruby/ruby/pull/423

[tmm1 (Aman Karmani)]

Based on feedback from ko1-san, I have modified the ruby signatures as follows:

• call-seq:

• ObjectSpace.dump(obj[, output: :string]) # => "{...}"

• ObjectSpace.dump(obj, output: :file) # => "/tmp/rubyobj000000"

• ObjectSpace.dump(obj, output: :stdout) # => nil

• call-seq:

• ObjectSpace.dump_all([output: :file]) # => "/tmp/rubyheap000000"

• ObjectSpace.dump_all(output: :stdout) # => nil

• ObjectSpace.dump_all(output: :string) # => "{...}\n{...}\n..."

If anyone has opinions on these APIs, I'd love to hear them.

[akahn (Alexander Kahn)]

I think it could be helpful to be able to specify the filename that the dump should be written to, or at least the directory.

[tmm1 (Aman Karmani)]

You can use something like this: FileUtils.mv(ObjectSpace.dump_all, "mydumpfile.json")

[tmm1 (Aman Karmani)]

• Status changed from Open to Closed
• % Done changed from 0 to 100

This issue was solved with changeset r43585.
Aman, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

---

• ext/objspace/object_tracing.c: Add experimental methods to dump
  objectspace as json: ObjectSpace.dump_all and ObjectSpace.dump(obj).
  These methods are useful for debugging reference leaks and memory growth
  in large ruby applications. [Bug #9026] [ruby-core:57893] [Fixes GH-423]