[erlang-questions] VM ends with 'killed'
Mon Mar 14 11:15:34 CET 2011
This may be related.
On Mar 14, 2011 6:08 PM, "tom kelly" <> 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,
> 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
> provided. We dismissed this as a cause for ages as we were catching the
> 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.
> On Mon, Mar 14, 2011 at 8:31 AM, Gordon Guthrie <
>> 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:
>> There is no crash dump. What do I do now? Where do I start debugging
>> Gordon Guthrie
>> CEO hypernumbers
>> t: hypernumbers
>> +44 7776 251669
>> erlang-questions (at) erlang.org mailing list.
>> See http://www.erlang.org/faq.html
>> To unsubscribe; mailto:
More information about the erlang-questions