Erlang shell crash

Raimo Niskanen raimo@REDACTED
Fri Jun 9 09:04:31 CEST 2006

Well first the standard questions:
* What is the Erlang/OTP release, or emulator version
* What is the application, or what kind of application is it?

When the emultor starts it pre-calculates the heap sizes
to use and puts them in an array. The calculated heap sizes
are up to ridiculouosly large sizes, so that if you would
need such large heaps you most probably have other problems.

You most probably have other problems.

Your emulator has allocated 578 Mbytes of memory and had
a gigantic process heap for one process. That process
must have eaten all memory. The question is if the 
emulator is leaking memory or if your application 
allocates memory that can not be reclaimed in a
garbage collection?

So, more info is needed.

And, there has been releases with a wee bit to small
pre-calculated heap sizes.

Locate the culprit process in the crash dump viewer and
try to find out what it is doing. Perhaps look at the
call stack. That may give something.

surindar.shanthi@REDACTED (Surindar Sivanesan) writes:

> Dear all,
> I'm running an Erlang application.
> After 12 hours, the erlang shell crashes with *Abnormal termination.*
> Then i have viewed the Erlang dump in the *Crash dump viewer*.
> The crash dump viewer has the following information.
> Slogan*:  no next heap size found: 148185174, offset 0.*
> Memory allocated: 606002043 bytes.
> Atoms : 7158.
> Processes : 703
> ETS tables : 45
> Funs : 442
> Please give me the reason for this crash.
> with regards,
> S.Surindar


/ Raimo Niskanen, Erlang/OTP, Ericsson AB

More information about the erlang-questions mailing list