Haskell doesn't use `glibc` (or any other libc) `malloc`,it uses its own heap which is managed separately. Even Haskell's `malloc` (used with FFI) uses Haskell's heap; it allocates a "pinned" block that can't be moved but can still be garbage collected. Any fragmentation issues would need to be fixed in the garbage collector.

Donations are via the Open Software Collective, https://opencollective.com/xmonad

On Tue, Feb 18, 2025 at 3:49 PM <amd.mobile@virgilio.it> wrote:

Hi
Thank you for developing xmonad , it's my daily wm and I just love it

I just wanna ask, before posting an incorrect new issue, if xmonad ever had , or have already parched, an old glibc bug I learned about:

https://www.youtube.com/watch?v=fjUvETEAnSI

https://github.com/KDE/kwin/commit/561199762f2440a2e00d7aec0aecf64dce5e729a

https://blog.cloudflare.com/the-effect-of-switching-to-tcmalloc-on-rocksdb-memory-use/

It seems a very common bug among graphical environments

Also, I'd like to donate something to the project, how can I do?

Thank you

Cheers