Examining Erlang crash dumps - how to account for all memory?

Question

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.

Us

Answer 1

There is an module called crashdump_viewer which is great for these kinds of analysis.

Another thing to keep in mind is that Heap+Stack is afaik in words, not bytes which would mean that you have to multiply Heap+Stack with 4 on 32 and 8 on 64 bit. Can't find a reference in the manual for this but Processes talks about it a bit.