<div>Thanks a lot for attention.</div><div><br></div><div>Yes, this is just an out of memory situation, sorry for spending your time. Crash dump was finally written in about 10 minutes and weighted 410 MB.<br></div><div><br>
</div><div>But yes, that was very unclear what erlang system
was
doing that 10 minutes. While trying to solve this 'mystery' I waited several minutes - suppose long cleanup operation. But never had enough patience to wait 10 minutes :)</div><div><br></div><div>Another question - how can I estimate size of data structures, and know more about internal erlang data structures?</div>
<div><br></div><div>For example, here: <a href="http://www.erlang.org/doc/efficiency_guide/advanced.html">http://www.erlang.org/doc/efficiency_guide/advanced.html</a> stated that 'float' takes 16 or even 24 bytes on 32/64 bit system respectively. Is that true? I just can't figure out for what reason float number (double, or even extended precision) can take whole lot of space...</div>
<br><div class="gmail_quote">2011/11/26 Björn-Egil Dahlberg <span dir="ltr"><<a href="mailto:wallentin.dahlberg@gmail.com">wallentin.dahlberg@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote"><div class="im">2011/11/26 Erik Søe Sørensen <span dir="ltr"><<a href="mailto:ess@trifork.com" target="_blank">ess@trifork.com</a>></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Still, I think there's a point in that the situation would be less mysterious if the error message about what caused the crash-dump was printed (and flushed) before the crash-dump is written out.<br></blockquote><div>
<br></div></div><div>I agree! =)</div><div><br></div><font color="#888888"><div>// Björn-Egil </div></font><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
________________________________________<br>
From: <a href="mailto:erlang-bugs-bounces@erlang.org" target="_blank">erlang-bugs-bounces@erlang.org</a> [<a href="mailto:erlang-bugs-bounces@erlang.org" target="_blank">erlang-bugs-bounces@erlang.org</a>] On Behalf Of Erik Søe Sørensen [<a href="mailto:ess@trifork.com" target="_blank">ess@trifork.com</a>]<br>
Sent: 26 November 2011 03:13<br>
To: Denis Nesterov; <a href="mailto:erlang-bugs@erlang.org" target="_blank">erlang-bugs@erlang.org</a><br>
Subject: Re: [erlang-bugs] Simple floating-point lists operation hungs Erlang system<br>
<div><br>
I can reproduce this on Linux (Intel(R) Core(TM)2 Duo CPU, 2.10GHz, 2GB).<br>
This was done using 4 processes and 750k elements; apparent deadlock happened within a couple of minutes (but see below).<br>
<br>
The OS threads of the Erlang VM are stuck doing this:<br>
</div>[snip]<br>
<div><div>_______________________________________________<br>
erlang-bugs mailing list<br>
<a href="mailto:erlang-bugs@erlang.org" target="_blank">erlang-bugs@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-bugs" target="_blank">http://erlang.org/mailman/listinfo/erlang-bugs</a><br>
</div></div></blockquote></div></div><br>
<br>_______________________________________________<br>
erlang-bugs mailing list<br>
<a href="mailto:erlang-bugs@erlang.org">erlang-bugs@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-bugs" target="_blank">http://erlang.org/mailman/listinfo/erlang-bugs</a><br>
<br></blockquote></div><br>