"RSS lies. Your process might not be using that memory. The allocator might be hoarding it."<p>Interesting writeup, but:<p>No, anonymous AI author. Your process <i>is</i> using that memory, for its allocator. Features like lower-latency allocations don't come for free, even when they turn out severely suboptimal for your particular case. Your <i>code</i> isn't using that memory, but a support library is. It is very much in your process.
I am wondering about the last part of glibc malloc. Isnt that exactly the problem reported for the last 10+ years with glibc? And the common solution is to use tcmalloc or jemalloc which hasnt these problems?
Claude write me a post-mortem. Make no mistakes. Add a big image of a hero banner instead of rendering it in HTML for some reason.<p>I use AI myself (it's essentially non-optional at work right now), and it's not like this is useless information, but god, I'm just so saturated of this writing style.
> I'm just so saturated of this writing style.<p>I saw at least one tense error, so much for the idea of intentionally introducing grammar mistakes to demonstrate personhood.
Dammit. For a long time, I was blissfully clueless about AI writing style. But I recently read something that screamed en-SLOP, and now I can't unsee it anywhere. It hit me immediately with this article.<p>I want to go back to being dumb and naive. Give me the blue pill, please!