From: alex.gaziev@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71601] [Ruby trunk - Bug #11593] Is it possible that ObjectSpace.dump_all catch dead objects?
Date: Fri, 20 Nov 2015 06:30:23 +0000 [thread overview]
Message-ID: <redmine.journal-54984.20151120063023.396612aace8f6954@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11593.20151014075358@ruby-lang.org
Issue #11593 has been updated by Alex Gaziev.
Ok, I understood. This issue can be closed now, thank you
----------------------------------------
Bug #11593: Is it possible that ObjectSpace.dump_all catch dead objects?
https://bugs.ruby-lang.org/issues/11593#change-54984
* Author: Alex Gaziev
* Status: Feedback
* Priority: Normal
* Assignee: Aman Gupta
* ruby -v: 2.2.3p173
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
Koichi, can you please help. There are lines in a dump that are not referenced by anyone else. And these are not ROOTs. For example, I'm looking in my dump by address of object and there is no other objects which have references to this object:
```
$ ag 0x7fc4adc55a20 dump.json
1812949:{"address":"0x7fc4adc55a20", "type":"DATA", "class":"0xaf6c70", "struct":"proc", "references":["0x7fc4adc55a48", "0x7fc504140390", "0x7fc4adc55a20", "0x7fc5041404d0"], "memsize":104}
```
How can it be? Is it a dead object who got in a dump or am I missing something?
---Files--------------------------------
dead_thread.rb (216 Bytes)
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2015-11-20 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11593.20151014075358@ruby-lang.org>
2015-10-14 7:53 ` [ruby-core:71085] [Ruby trunk - Bug #11593] [Open] Is it possible that ObjectSpace.dump_all catch dead objects? alex.gaziev
2015-10-14 8:46 ` [ruby-core:71086] [Ruby trunk - Bug #11593] " alex.gaziev
2015-11-19 6:40 ` [ruby-core:71570] " ko1
2015-11-19 8:16 ` [ruby-core:71577] " alex.gaziev
2015-11-19 13:32 ` [ruby-core:71586] [Ruby trunk - Bug #11593] [Feedback] " ko1
2015-11-20 6:30 ` alex.gaziev [this message]
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-54984.20151120063023.396612aace8f6954@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).