You’re absolutely correct, in this manner of development you just hit a wall and call it a day. A few years back I read quite a few papers on NASA’s developmen

You’re absolutely correct, in this manner of development you just hit a wall and call it a day. A few years back I read quite a few papers on NASA’s development standards and did quite a bit of kernel dev also. I no longer do any allocations on daemonized or driver code like this. It’s far better to preallocate pools, store temp objects on stack and generally never malloc outside of the pool management. When we hit the alloc wall, we now have well-defined behaviors and can gracefully choose whether to reject, clean or error out. Additionally our code is generally more performant, less buggy, and easier to debug.