[erlang-questions] VM ends with 'killed'

[Edward Wang]

http://erlang.2086793.n4.nabble.com/Patch-for-18-exabyte-memory-allocation-failure-td3342133.html

This may be related.

Edward.
On Mar 14, 2011 6:08 PM, "tom kelly" <ttom.kelly@REDACTED> wrote:
> Hi Gordon,
>
> We had a crash matching this description on our system a while ago.
> We got some good hints as to what was happening from the system logs,
> especially:
> /var/log/messages
> /var/log/syslog
>
> In our case we were getting segmentation faults. We had been sending more
> data in a TCP packet than would fit into it with the "packet" option we
had
> provided. We dismissed this as a cause for ages as we were catching the
exit
> message when we did a binary_to _term on the data.
> Once we figured out what was happening we consulted the release notes and
> found out that the Erlang VM had already been fixed so it's probably not
> your problem.
>
> Hope this helps.
> //Tom.
>
>
> On Mon, Mar 14, 2011 at 8:31 AM, Gordon Guthrie <gordon@REDACTED
>wrote:
>
>> Folks
>>
>> I have been trying to resolve some run time issues. We are running a
>> big data load and the VM was crashing due to memory running out.
>>
>> The first issue was a runaway message queue - so we put in a limiter
>> that checked that processes message queue and waited til it cleared if
>> there was overload.
>>
>> The problem moved to another process whose heap would grow and grow.
>> Adding a check on the heap size and forced garbage collect appeared to
>> be the answer.
>>
>> But now when I run the load, after adding most of the data the VM
>> suddenly ends with the stark message:
>> Killed
>> [End]
>>
>> There is no crash dump. What do I do now? Where do I start debugging
this?
>>
>> Gordon
>>
>> --
>> Gordon Guthrie
>> CEO hypernumbers
>>
>> http://hypernumbers.com
>> t: hypernumbers
>> +44 7776 251669
>>
>> ________________________________________________________________
>> erlang-questions (at) erlang.org mailing list.
>> See http://www.erlang.org/faq.html
>> To unsubscribe; mailto:erlang-questions-unsubscribe@REDACTED
>>
>>