What is the policy on out-of-memory?

[Havoc Pennington]

Exactly, the out-of-memory should be propagated to the app. Most apps
just ignore it, of course. But if there's a retry it happens at the
app level.

Havoc

On Mon, Jan 12, 2009 at 9:50 AM, Scott James Remnant
<scott at canonical.com> wrote:
> On Sun, 2009-01-11 at 21:58 -0800, Ryan Saunders wrote:
>
>> While hacking inside of DBus, I've repeatedly encountered places in
>> the code where it attempts to handle out-of-memory conditions,
>> returning FALSE to indicate OOM. I understand propagating this out of
>> low level functions, but how & when does/should DBus decide to
>> re-attempt an operation that failed due to OOM? Should the top-level
>> auth code repeatedly (endlessly?) retry in the face of an OOM
>> condition? Should it propagate back out to the transport layer? To the
>> connection layer? All the way back to the client or server app?
>>
> Generally speaking, most OOM situations are reported back to the calling
> program and it's up to you to deal with it as you see fit (e.g. by
> spinning, or calling abort, etc.)
>
> Scott
>