On Tue, Nov 6, 2012 at 6:19 PM, Jason Evans <[email protected]> wrote:
> This is the first I've heard of such an issue. If you are able to narrow > down the failure mode, please let me know so that we can get this fixed ASAP. Thank you Jason, given that this is a new issue I'll investigate further to understand if it could be an issue with Redis itself (I think every single allocation is wrapped in order to abort Redis on out of memory, but I'll double check this). If it still seems a jemalloc issue I'll see if I can reproduce it, so far the only way to reproduce the issue is loading a large database file on a 32 bit Linux system N times: most of the times it crashes for out-of-memory, a few times it crashes with an unexpected signal 11 or failed assertion. Cheers, Salvatore -- Salvatore 'antirez' Sanfilippo open source developer - VMware http://invece.org 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 _______________________________________________ jemalloc-discuss mailing list [email protected] http://www.canonware.com/mailman/listinfo/jemalloc-discuss
