[erlang-questions] Getting more info from crash dump file
Thu Dec 13 10:21:35 CET 2012
I got an erlang crash dump file on a 2G memory linux with following info:
eheap_alloc: Cannot allocate 78362800 bytes of memory (of type "heap").
The total memory consumed by the VM was about 1.5G and most of them were used by process. According to the process info in the dump file, the biggest Stack+Heap was 15672560 and the owner's state was garbing. I am not sure whether the process was the killer of the whole VM.
Name Spawned as proc_lib:init_p/5
State Garbing (limited info) Last scheduled in for xmerl_scan:'-initial_state0/2-fun-1-'/2
Started Tue Nov 6 17:00:39 2012 Spawned by <0.48.0>
Stack+heap 15672560 OldHeap 8024355
Heap unused 202 OldHeap unused 8024355
Number of heap fragments 1 Heap fragment data 119
Program counter 0x02ea24dc (xmerl_scan:'-initial_state0/2-fun-1-'/2 + 4)
Continuation pointer 0x02e8a254 (xmerl_scan:scan_char_data/5 + 2408)
Link list [#Port<0.16239279>, <0.48.0>]
Msg queue length 0
Is there a way to find out which process or function call was the reason of the allocating action, and how can I get more info from the dump file to help locating the error?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions