From: Sam Saffron <sam.saffron@gmail.com>
To: Ruby users <ruby-talk@ruby-lang.org>
Cc: mwrap-public@80x24.org
Subject: Re: [ANN] mwrap - LD_PRELOAD malloc wrapper + line stats for Ruby
Date: Tue, 3 Jul 2018 10:11:21 +1000 [thread overview]
Message-ID: <CAAtdryNexZtjU=Fr1QjFVJWJ8eN5ASLs8xox54dD1ogqEzf8ew@mail.gmail.com> (raw)
In-Reply-To: <20180702120050.GA24029@dcvr>
Awesome Eric!
I just ran this on a simple "Discourse boot" and got:
https://gist.githubusercontent.com/SamSaffron/220910a8fb7abd1226c3e9eb0c447ef4/raw/53af7bb83c4ebe58e51b0cee862048b2e47995ad/sorted.txt
It is fascinating to see absolute complete accounting with lines like:
301056 147 /usr/lib/x86_64-linux-gnu/libpq.so.5(+0x1324a) [0x7efd84d3824a]
This is information that is hidden from
`ObjectSpace#trace_object_allocations`. Complete accounting opens up a
whole bunch of possibilities, we could for example compare with Ruby
accounting and find memory that is not being reported to Ruby
properly.
Is there any chance we can have a mode with "free" tracking as well?
That way we can enable this on a long running process to detect leaks?
It also makes c level leaks way easier to debug, cause we can listen
on a signal and dump a log on it. Then comparing 2 logs can give us a
leak very very easily. (we could add mwrap --compare dump1 dump2 to
ease this usage)
Also per:
344809221 1070570
/home/sam/.rbenv/versions/master/lib/ruby/gems/2.6.0/gems/activesupport-5.2.0/lib/active_support/dependencies.rb:283
39139224 26553
/home/sam/.rbenv/versions/master/lib/ruby/gems/2.6.0/gems/activesupport-5.2.0/lib/active_support/dependencies.rb:277
I wonder if there is any way we can get slightly better reporting
here, I am guessing this is just around loading of code, but I wonder
if we could break that down in a cleaner way here?
next prev parent reply other threads:[~2018-07-03 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 12:00 [ANN] mwrap - LD_PRELOAD malloc wrapper + line stats for Ruby Eric Wong
2018-07-03 0:11 ` Sam Saffron [this message]
2018-07-03 7:48 ` Eric Wong
2018-07-16 21:48 ` Eric Wong
2018-07-03 9:11 ` Eric Wong
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://80x24.org/mwrap/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAtdryNexZtjU=Fr1QjFVJWJ8eN5ASLs8xox54dD1ogqEzf8ew@mail.gmail.com' \
--to=sam.saffron@gmail.com \
--cc=mwrap-public@80x24.org \
--cc=ruby-talk@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mwrap.git/
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).