Memory corruptions near 32 bit limits

Salvatore Sanfilippo antirez at
Tue Nov 6 03:01:31 PST 2012


in the Redis community it was observed multiple times that when a 32
bit instance using Jemalloc (<= 3.0) is very near to be out of memory
because the whole available address space was used, it can happen that
the server crashes because memory gets corrupted instead of malloc
returning NULL.

Is this a known issues?

Redis 2.6 automatically sets a 3GB memory limit in 32 bit instances
now so we are likely to see this less frequently in the future, but it
is interesting for us to understand this issue as sometimes this
triggered investigations about non existing bugs.


Salvatore 'antirez' Sanfilippo
open source developer - VMware

Beauty is more important in computing than anywhere else in technology
because software is so complicated. Beauty is the ultimate defence
against complexity.
       — David Gelernter

More information about the jemalloc-discuss mailing list