The thing that bugs me about this is that I'm pretty sure there is some way to make a damned good effort at at least saving results out to disk or dying gracefully even when malloc starts asploding.
Also, this means that I can screw up other processes for no good reason, even though only my proc should get killed for going over quota.
"Mappings are overcommited because mappings are routinely undercommitted"
Could you please explain this again? I'm not quite sure I parsed that out correctly. Thanks!
So, if I'm reading this correctly, my usual null-checking of malloc() returns is insufficient?
What the hell? How did this ever get put in?
As an application developer trying to write code that can run on machines I have no control over, how is this reasonable? This seems like it pretty much neuters my ability to accurately detect potential out-of-memory conditions with a hackish workaround.
Also, this means that I can screw up other processes for no good reason, even though only my proc should get killed for going over quota.
"Mappings are overcommited because mappings are routinely undercommitted"
Could you please explain this again? I'm not quite sure I parsed that out correctly. Thanks!