2 ms·
The glibc memory allocator DOES have pathological cases that lead to what can look like memory leaks. See https://glandium.org/blog/?p=3698 https://glandium.org
by glandium 2y ago
The glibc memory allocator DOES have pathological cases that lead to what can look like memory leaks. See https://glandium.org/blog/?p=3698 https://glandium.org/blog/?p=3698 https://glandium.org/blog/?p=3723 https://glandium.org/blog/?p=3723 https://sourceware.org/bugzilla/show_bug.cgi?id=23416 https://sourceware.org/bugzilla/show_bug.cgi?id=23416 (despite being rather old, it's also still a problem)
- wengo314 2y agoFWIW i had it with icinga2. so now they actually preload jemalloc in the service file to mitigate the issue, this may very well be what you're talking about in case someone is interested: https://github.com/Icinga/icinga2/issues/8737 https://github.com/Icinga/icinga2/issues/8737 (basically using jemalloc was the big fix) https://icinga.com/docs/icinga-2/latest/doc/15-troubleshooting/#try-swapping-out-the-allocator https://icinga.com/docs/icinga-2/latest/doc/15-troubleshooti...