logoalt Hacker News

xxstoday at 7:22 PM1 replyview on HN

Few months back, some of the services switched to jemalloc for the Java VM. It took months (of memory dumps and tracing sys-calls) to blame the JVM, itself, for getting killed by the oom_killer.

Initially the idea was diagnostics, instead the the problem disappeared on its own.


Replies

yxhuvudtoday at 8:27 PM

If you changed from glibc to jemalloc and that solved your issues, then you should blame glibc, not the JVM.

show 1 reply