On Tue, Sep 27, 2016 at 03:10:17PM +0200, Florian Weimer wrote: > * Fernando Santagata: > > >> Usually it manifests in premature OOM killer invocations, but maybe > >> something the reporter's system configuration changes that (perhaps it > >> runs with vm.overcommit_memory=2?). > > > > That's it. I found this in /var/log/kern.log at the time I run a program > > that crashed: > > > > Sep 27 10:37:31 gretux kernel: [ 77.250470] mmap: moar (2564): VmData > > 135217152 exceed data ulimit 134217728. Update limits or use boot > > option ignore_rlimit_data. > > No, I think the above is unrelated. It relates to a userspace ABI > break related to the RLIMIT_DATA implementation.
Anyway, booting with the 4.6.0 kernel solves all the issues. Thanks for the help! -- Fernando Santagata