On 11/10/2015 06:56 PM, Donald Sharp wrote: > What is Quagga's approach to OOM situations? Here we are crash-n-burning, > if that is ok, Consider it acked :)
Since XMALLOC calls abort() if it can't allocate memory, my current understanding is that it can be assumed XMALLOC will not return NULL, and the daemon will abort by design in an OOM situation. While it is probably possible to do something more elaborate in many OOM situations, like logging the issue but continuing with operation as good as possible, I think that almost nothing of the codebase has been written with the idea in mind that it might have to continue running with depleted heap space. -Christian _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
