[erlang-bugs] Simple floating-point lists operation hungs Erlang system
Sat Nov 26 21:13:03 CET 2011
Thanks a lot for attention.
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.
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
Another question - how can I estimate size of data structures, and know
more about internal erlang data structures?
For example, here:
'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...
2011/11/26 Björn-Egil Dahlberg <>
> 2011/11/26 Erik Søe Sørensen <>
>> 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.
> I agree! =)
> // Björn-Egil
>> From:  On
>> Behalf Of Erik Søe Sørensen 
>> Sent: 26 November 2011 03:13
>> To: Denis Nesterov;
>> Subject: Re: [erlang-bugs] Simple floating-point lists operation hungs
>> Erlang system
>> I can reproduce this on Linux (Intel(R) Core(TM)2 Duo CPU, 2.10GHz, 2GB).
>> This was done using 4 processes and 750k elements; apparent deadlock
>> happened within a couple of minutes (but see below).
>> The OS threads of the Erlang VM are stuck doing this:
>> erlang-bugs mailing list
> erlang-bugs mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-bugs