[erlang-questions] Erlang VM Crash and Heart doesn't restart

Eric Boyer eric.boyer@REDACTED
Tue Jan 22 16:38:58 CET 2013

Hi there,

We're running R15B02 on Windows Server 2008 R2 on a mainly IO bound
application. Occasionally when it get busy processing hundreds of files it
will crash with the following event log entry:

Faulting application name: erl.exe, version:, time stamp: 0x504492cf
Faulting module name: beam.smp.dll, version:, time stamp: 0x50449201
Exception code: 0xc0000005
Fault offset: 0x00000000000c75f2
Faulting process id: 0x9d3c
Faulting application start time: 0x01cdf82413c26aeb

There is no erl_crash.dump generated and the heart process does not restart
the vm. Are there any ideas as to why this is happening or what can be done
so that heart can properly restart the vm? I see the heart.exe process
active with the correct pid for the erlang process but it doesn't seem to
work in this case.


Additional Information:

vm.args is:

## Name of the node
-name <snip>

## Cookie for distributed erlang
-setcookie <snip>

## Heartbeat management; auto-restarts VM if it dies or becomes unresponsive
## (Disabled by default..use with caution!)

## Enable kernel poll and a few async threads
+K true
+A 32
+P 1000000

## Increase number of concurrent ports/sockets
-env ERL_MAX_PORTS 100000

## Tweak GC to run more often

os:getenv("HEART_COMMAND") returns:

%node_root%\bin\%node_name%.cmd start
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130122/deea00af/attachment.htm>

More information about the erlang-questions mailing list