[erlang-questions] Examining Erlang crash dumps - how to account for all memory?
Sat Jul 9 07:14:40 CEST 2011
Certain objects, such as binaries and ets tables, live in different memory
than that of each process. If you have lots of those, then that might
explain the rest of the memory.
Also, if you look at what each process is doing, is any process "garbing"?
If so, it probably is using more memory temporarily for the new block it's
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world. Nevertheless,
whether we get there willingly or not, we shall soon have lower consumption
rates, because our present rates are unsustainable.
On Fri, Jul 8, 2011 at 7:28 AM, Magnus Falk <magnus.falk@REDACTED> wrote:
> This is a copy of a question I asked over at StackOverflow that noone has
> been able to answer yet:
> I've been poring over this Erlang crash dump where the VM has run out of
> heap memory. The problem is that there is no obvious culprit allocating all
> that memory.
> Using some serious black awk magic I've summed up the fields Stack+heap,
> OldHeap, Heap unused and OldHeap unused for each process and ranked them by
> memory usage. The problem is that this number doesn't come even close to the
> number that is representing the total memory for all the processes
> processes_used according to the Erlang crash dump guide.
> I've already tried the Crashdump Viewer and either I'm missing something or
> there isn't much help there for my kind of problem.
> The number I get is 525 MB whereas the processes_used value is at 1348 MB.
> Where can I find the rest of the memory?
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions