<html><head></head><body><div class="ydp190c1f65yahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 13px;"><div></div>
<div dir="ltr" data-setdir="false">This used to be possible via the instrument module but the functionality got removed in OTP21, I used this functionality to detect a large binheap leak in jiffy way back when. Theres a lengthy discussion here under a PR called "improve instrumentation" but it really just "removed instrumentation" <span><a href="https://github.com/erlang/otp/pull/1790" rel="nofollow" target="_blank" class="">https://github.com/erlang/otp/pull/1790</a>.<br></span><div><br></div><div dir="ltr" data-setdir="false">There are BIF debug functions under hipe that can print this information. hipe_bifs:show_heap/1 and friends.</div></div>
</div><div id="yahoo_quoted_6777507682" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, April 8, 2020, 02:53:49 p.m. EDT, Dániel Szoboszlay <dszoboszlay@gmail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv5226392344"><div><div dir="ltr">Hi,<div><br clear="none"></div><div>Even though you cannot trace on allocating large binaries, you may try tracing garbage collections, and look for GC-s that clean up a lot of off-heap binary data. This could at least narrow done the search for some processes, although it won't tell you where the allocation happens. But maybe once you know which processes are guilty you will be able to add more targeted tracing until you find the root cause.</div><div><br clear="none"></div><div>Cheers,</div><div>Daniel</div></div><br clear="none"><div class="yiv5226392344yqt1049329809" id="yiv5226392344yqt83720"><div class="yiv5226392344gmail_quote"><div class="yiv5226392344gmail_attr" dir="ltr">On Wed, 8 Apr 2020 at 16:14, Lukas Larsson <<a rel="nofollow" shape="rect" ymailto="mailto:lukas@erlang.org" target="_blank" href="mailto:lukas@erlang.org">lukas@erlang.org</a>> wrote:<br clear="none"></div><blockquote class="yiv5226392344gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div dir="ltr"><div>Hello,</div><br clear="none"><div class="yiv5226392344gmail_quote"><div class="yiv5226392344gmail_attr" dir="ltr">On Tue, Apr 7, 2020 at 9:26 AM Devon Estes <<a rel="nofollow" shape="rect" ymailto="mailto:devon.c.estes@gmail.com" target="_blank" href="mailto:devon.c.estes@gmail.com">devon.c.estes@gmail.com</a>> wrote:<br clear="none"></div><blockquote class="yiv5226392344gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div>Hi all,</div><div><br clear="none"></div><div>I’m seeing some cases in my application where our off-process binary heap allocation jumps by several orders of magnitude and then goes down right after. I’m sure this is something that’s in our app just loading dozens of huge binaries into memory at once and not a bug in anything underlying or a binary leak, but finding where these allocations are happening so I can make some changes to avoid this has so far not yielded any results. Ideally I’d like to be able to set a trace with something like erlang:trace/3 on some function that sends a tracer message whenever a binary over 30MB is allocated and includes the call stack or even just the calling function that allocated the binary in the trace message. </div></blockquote><blockquote class="yiv5226392344gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div><br clear="none"></div><div>Going through the binary vheap and getting a list of the processes that have references to those binaries won’t help in this case.</div><div><br clear="none"></div><div>Is such a trace possible? Is there some flag I can set when starting my BEAM process to give me some kind of debug output that would give me this information? I’d imagine this is all in C, so it might be a bit tricky...</div></blockquote><div><br clear="none"></div><div>No it is not possible without modifying the VM. I can't think of any good way to get this information without scanning the process' vheap, which as you say would not help much in this case.</div><div></div><div><br clear="none"></div><blockquote class="yiv5226392344gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;"><div><br clear="none"></div><div>Thanks in advance for the help!</div><div><br clear="none"></div><div>Cheers,</div><div>Devon</div>-- <br clear="none"><div dir="ltr"><div dir="ltr"><br clear="none">_________________<br clear="none">Devon Estes<br clear="none"><a rel="nofollow" shape="rect" target="_blank" onclick="return window.theMainWindow.showLinkWarning(this)" href="http://203.559.0323">203.559.0323</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="http://www.devonestes.com">www.devonestes.com</a><br clear="none"><br clear="none"></div></div>
</blockquote></div></div>
</blockquote></div></div></div></div></div>
</div>
</div></body></html>