LINUX Server Reboot Frequency 7374

And what does "free" say? Orproc-meminfo, when doing such large allocations? OK, so you'd have to do an allocation large enough to go past the system RAM and get into swap to really see it happen. But as I understand it, that memory is still relegated to that program, and is available *for that program*. At least, that's how I remember building stacks from scratch: if someone's invented a way to actually release it to the system instead of merely for that program's use in its own stack, I'm going to be *VERY* surprised.

And in fact, you can even get away with doing that for quite a while: the memory allocated will wind up being heavily in swap, and if it's not actually being used for much, most of it will be swapped out at any given time.

OK, that makes more sense: by freeing up unused stuff off what is effectively the end of the stack, that could work for releasing the resources.

Who knows? It's closed source, very proprietary, multi-platform, and clearly written for big iron, not casual implementation by any means. Using its own memory management makes sense, but at some point you sort of *have* to talk to glibc unless you want to rewrite a lot of very, very basic functions from scratch.