[asterisk-dev] policy change for correct handling of fatal program conditions

[Tilghman Lesher]

On Wednesday 24 January 2007 02:44, SF Markus Elfring wrote:
> > No, but other threads should observe the same principle.  If they are
> > unable to allocate sufficient space to continue the call, then they
> > should abort their own call only, possibly logging that information.  At
> > no point should any call thread abort processing for another call thread.
> >  It's probable that, at some point, enough memory will be freed to
> > continue the processing of some existing calls.
>
> You seem to be optimistic that a call or the complete process can still
> make forward progress after a failed memory allocation. I've got doubts
> about correct behaviour.

Well, if not, then all calls fail in their own due time.  This is still the
"right thing" to do, and you have not made an argument for why the process
would do better to call exit().

-- 
Tilghman