<div>I'm using Eralng emulator version is 5.4.3.</div>
<div>The type of application is load testing with simulator in one PC ( which has multiple thread. At that monent we have 200 threads) which sends requests to the server in another PC.</div>
<div>The Shell running as server is collapsed.</div>
<div>-with regards,<br> S.Surindar<br><br> </div>
<div><span class="gmail_quote">On 09 Jun 2006 09:04:31 +0200, <b class="gmail_sendername">Raimo Niskanen</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Well first the standard questions:<br>* What is the Erlang/OTP release, or emulator version<br>erlang:system_info(system_version)?
<br>* What is the application, or what kind of application is it?<br><br>When the emultor starts it pre-calculates the heap sizes<br>to use and puts them in an array. The calculated heap sizes<br>are up to ridiculouosly large sizes, so that if you would
<br>need such large heaps you most probably have other problems.<br><br>You most probably have other problems.<br><br>Your emulator has allocated 578 Mbytes of memory and had<br>a gigantic process heap for one process. That process
<br>must have eaten all memory. The question is if the<br>emulator is leaking memory or if your application<br>allocates memory that can not be reclaimed in a<br>garbage collection?<br><br>So, more info is needed.<br><br>
And, there has been releases with a wee bit to small<br>pre-calculated heap sizes.<br><br>Locate the culprit process in the crash dump viewer and<br>try to find out what it is doing. Perhaps look at the<br>call stack. That may give something.
<br><br><br><br><a href="mailto:email@example.com">firstname.lastname@example.org</a> (Surindar Sivanesan) writes:<br><br>> Dear all,<br>> I'm running an Erlang application.<br>> After 12 hours, the erlang shell crashes with *Abnormal termination.*
<br>> Then i have viewed the Erlang dump in the *Crash dump viewer*.<br>> The crash dump viewer has the following information.<br>><br>> Slogan*: no next heap size found: 148185174, offset 0.*<br>> Memory allocated: 606002043 bytes.
<br>> Atoms : 7158.<br>> Processes : 703<br>> ETS tables : 45<br>> Funs : 442<br>><br>> Please give me the reason for this crash.<br>><br>><br>> with regards,<br>> S.Surindar<br><br>--<br><br>
/ Raimo Niskanen, Erlang/OTP, Ericsson AB<br></blockquote></div><br><br clear="all"><br>-- <br>with regards,<br>S.Surindar