ejabberd - Comments for "Ejabberd 2.0.1 crashes when process memory reach close to 2GB in Linux"

Re: Erlang 2GB memory limit on 32bit processor

zinid — Sat, 06 Feb 2010 16:26:06 +0000

Quote:

I'm wondering why this limitation is maintained in Erlang?
why not relaxed this limitation based on OS? since linux support more than 2GB address space should not the erlang runtime depend on it?

No idea. You better ask Erlang developers about that.

Erlang 2GB memory limit on 32bit processor

GP — Thu, 04 Feb 2010 12:54:17 +0000

I'm wondering why this limitation is maintained in Erlang?
why not relaxed this limitation based on OS? since linux support more than 2GB address space should not the erlang runtime depend on it?

Compiled Erlang on 64bit

GP — Wed, 03 Feb 2010 15:02:48 +0000

Compiled Erlang on 64bit Linux machine and not able to reproduce the issue using jabsimul stress test tool...the memory consumption of ejabberd process crossed more than 2GB even sometime 3GB with heavy load...require some more testing, will update soon

Thanks once again, Zinid

Re: Ejabberd 2.0.1 crashes when process memory

zinid — Tue, 02 Feb 2010 02:10:37 +0000

Quote:

Does Linux has the 2GB process memory limitation something similar in windows?

This is a limitation of Erlang: it is unable to allocate more than 2-2.5Gb of heap on 32-bit machine.

Quote:

Do we can run 64-bit erlang in 32 linux machine?

I think no.

Thanks for response,

GP — Mon, 01 Feb 2010 17:16:15 +0000

Thanks for response, Zinid.

erlang:system_info(wordsize) returned 4,

we use Linux 32 bit multi-core processor machine with ejabberd 2.0.1 and erlang R12B-5 build from the source.

Does Linux has the 2GB process memory limitation something similar in windows? Also the message queue length is zero across the crash dump

Do we can run 64-bit erlang in 32 linux machine?

Re: Ejabberd 2.0.1 crashes when process memory reach

zinid — Mon, 01 Feb 2010 16:19:48 +0000

Make sure you're using 64-bit Erlang. To check that, run:
$ erl
1> erlang:system_info(wordsize).
8
Here 8 means 64-bit Erlang is used. This is important because of limitation of memory allocation on 32-bit platforms.
In your crash dumps you should find memory consuming process. Typically there are only 1 or 2 such processes. To do that grep the crashdump with 'Message queue length' pattern, sort the result. Copy the snippet from =proc: to =proc: of most consuming process and paste it here.
Please tell us the version of your ejabberd and Erlang.