[erlang-questions] Crash on alloc

Valentin Micic v@REDACTED
Sat Feb 7 07:41:44 CET 2009


Hmmm... just tried it on windoze with mixed results:

Erlang (BEAM) emulator version 5.6.5 [smp:2] [async-threads:0]

Allocates the memory and then crashes. OTOH:

Erlang (BEAM) emulator version 5.5.4 [async-threads:0]

Note that 5.5.4 does not have smp support. Then I got my imagination going,
so I've started 5.6.5 with SMP support and the thing worked.

Erlang (BEAM) emulator version 5.6.5 [async-threads:0] Eshell V5.6.5  (abort
with ^G) (gsmat@REDACTED)1> {lists:seq(3, 40000000, 2), lists:seq(3,
40000000, 2)}.
{[3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,
  43,45,47,49,51,53,55,57|...],
 [3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,
  45,47,49,51,53,55|...]}
(gsmat@REDACTED)2>

Hope this helps someone, somewhat, somewhere.

V

-----Original Message-----
From: erlang-questions-bounces@REDACTED
[mailto:erlang-questions-bounces@REDACTED] On Behalf Of Michael McDaniel
Sent: 06 February 2009 09:47 PM
To: erlang-questions@REDACTED
Subject: Re: [erlang-questions] Crash on alloc


 I only have 1/2 GB memory and the operation works ...


mmcdanie@REDACTED:~$ erl
Erlang (BEAM) emulator version 5.6.5 [async-threads:0] [hipe]
[kernel-poll:false]

Eshell V5.6.5  (abort with ^G)
1> {lists:seq(3, 40000000, 2), lists:seq(3, 40000000, 2)}.
{[3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,
  43,45,47,49,51,53,55,57|...],
 [3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,
  45,47,49,51,53,55|...]}
2> q().
ok
3> mmcdanie@REDACTED:~$ uname -a
Linux phemora 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
GNU/Linux

mmcdanie@REDACTED:~$ dmesg | egrep Memory
[    0.004000] Memory: 472772k/491456k available (2572k kernel code, 18024k
reserved, 1160k data, 424k init, 0k highmem)

mmcdanie@REDACTED:~$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 3839
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 3839
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


~M


On Fri, Feb 06, 2009 at 07:46:41PM +0100, Jachym Holecek wrote:
> # Imre Palik 2009-02-06:
> > Feladó: Francesco Cesarini (Erlang Training and Consulting)
[francesco@REDACTED]
> > >
> > > This is the standard behaviour when the VM runs out of memory.... Try
> > > generating smaller lists or adding more memory to your computer.
> > 
> > I have 3 Gigs, and as far as I can see, this fails on an alloc of less
then 400 Megs. Does this quite reliably, even as the first command of the
shell.
> 
> Assuming you're running a Unix-like OS: try increasing your data area
> limit (man ulimit).
> 
> 	-- Jachym
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions

-- 
Michael McDaniel
Portland, Oregon, USA
http://trip.autosys.us
http://autosys.us

_______________________________________________
erlang-questions mailing list
erlang-questions@REDACTED
http://www.erlang.org/mailman/listinfo/erlang-questions




More information about the erlang-questions mailing list