Thanks Willy!

wt., 25 mar 2025 o 18:44 Willy Tarreau <w...@1wt.eu> napisaƂ(a):

> OK actually it's not a segfault, it's a watchdog during malloc_trim().
> We've seen a few over time, as some libc can become extremely slow
> during this operation and may even never complete if there are
> sufficient threads trying to allocate memory while this one is
> purging its entries. Unfortunately we can't ask it to only purge
> a little bit of them.
>
> We've added a global option "no-memory-trimming" explicitly to
> disable this mechanism. We don't want to remove it for everyone
> because for some users on small systems it can be vital. But with
> high loads, the allocator can be put under quite some stress and
> then it's better to disable trimming.
>

Actually this happened during DDoS, so HAProxy and the server were heavily
loaded. Now it makes perfect sense. Thanks a lot for the explanation!

Kind regards,

Reply via email to