Http://www.cnblogs.com/me-sa/archive/2012/04/28/2475556.html
Erlang Crash Dump Viewer is really the wrong Pyle artifact, remember we discussed earlier [Erlang 0013] Crawl Erlang process runtime information [Erlang 0012]erlang process input queue, Here is the document I combed for "how to interpret the Erlang crash dumps";
A lot of people are asking what tools are available to open crash_dump files? or analyze crash_dump files, in fact, quite simple, a command can be:
| 12 |
1> crashdump_viewer:start().WebTool isavailable at http://localhost:8888/ |
Google reader stopped, Yunio free service also stopped, these days there is no service is reliable, said stop on the stop, the following link is all invalid, I re-upload a copy:
Http://files.cnblogs.com/me-sa/Erlang_Crash_Dump.pdf
Use the recon erl_crashdump_analyzer.sh as follows:
Project Address: https://github.com/ferd/recon/blob/master/script/erl_crashdump_analyzer.sh
| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758 |
$ ./recon/script/erl_crashdump_analyzer.sh erl_crash.dump analyzing erl_crash.dump, generated on: Thu Apr 17 18:34:53 2014 Slogan: eheap_alloc: Cannot allocate 2733560184 bytes of memory (of type "old_heap"). Memory: === processes: 2912 Mb processes_used: 2912 Mb system: 8167 Mb atom: 0 Mb atom_used: 0 Mb binary: 3243 Mb code: 11 Mb ets: 4755 Mb --- total: 11079 Mb Different message queue lengths (5 largest differen t): === 1 5010932 2 159 5 158 49 157 4 156 Error logger queue length: === 0 File descriptors open: === UDP: 0 TCP: 19951 Files: 2 --- Total: 19953 Number of processes: === 36496 Processes Heap+Sta ck memo ry siz es (wor ds) us ed inthe VM (5 largest different): === 1 284745853 1 5157867 1 4298223 2 196650 12 121536 Processes OldHeap memory sizes (words) used inthe VM (5 largest different): === 3 318187 9 196650 14 121536 64 75113 15 46422 Process States when crashing (sum): === 1 Garbing 74 Scheduled 36421 Waiting------------------------------------------------------------ |
The official address is: http://www.erlang.org/doc/apps/erts/crash_dump.html
[Erlang 0057] Erlang debug: Erlang Crash Dump Viewer