Hey Jeff, I had to double check because I couldn't believe this was you. I'm a big fan of the Jeff and Casey Show! The problem with doing custom allocation is

Hey Jeff, I had to double check because I couldn't believe this was you. I'm a big fan of the Jeff and Casey Show! The problem with doing custom allocation is not specifically due to bugs in the allocator per se, but because your custom allocator will probably not be hardened against other bugs like some other allocators are. Specifically you will piss off the OpenBSD people who have put a lot of work into their allocator with "exploit mitigations." A bump allocator is pretty much guaranteed to let overflows (reads and writes) touch other valid memory. A hardened allocator will use guard pages and other tricks to prevent those bugs from being exploitable. One thing you can do is use bump allocators within "security zones." For example data related to a single user can be allocated together without much risk, but data from separate users is kept separate. This is very different from the world of game programming. I've been wondering lately if there will be some sort of bifurcation of the field.