https://bugs.openldap.org/show_bug.cgi?id=9365
--- Comment #10 from Ondřej Kuzník ondra@mistotebe.net --- On Wed, Apr 27, 2022 at 01:38:48PM +0000, openldap-its@openldap.org wrote:
Unfortunately this issue is still present, e.g. when running 2.6.1 on Ubuntu 20.04 (Focal) and eventually even 22.04 (Jammy).
The customer provided jemalloc profiler call-graphs from the running production env. Are these interesting to look at?
If you have several profiles from the same run as the memory use is going up, pprof with --base should be able to show who the additional memory belongs to. That might help pinpoint the code responsible.
Thanks,