Mike Hearn wrote:
OOM safety is a bit complicated, you have to properly unwind the stack and
restore state as you go - for instance the last patch I submitted fixed a
bug where OOM would not cause the loop to terminate, but I forgot to free
some data as we returned up the stack.
Given that it can be quite complex and introduce new bugs, and given that
it's really quite a useless feature IMHO as modern Linux boxes will hang
themselves in swap hell before returning NULL from malloc I don't think
this should be a janitorial project.
You can get NULL with a corrupted heap too.
Rob
