[toast0]

erlang:process_info(Pid, binary) for all processes with some post processing was usually pretty helpful for me, although I don't think it tells you much about ets tables, which is where my big bloat usually was. If you store binaries in ets (or mnesia) and the binaries live for a long time, it's useful to run them through binary:copy/1 if the binary is a sub-binary that references a large binary that's otherwise garbage. Or at least this used to be useful; sometimes my experiencs get obsoleted when OTP updates have efficiency changes.