What is the policy on out-of-memory?

[Scott James Remnant]

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
-- 
Scott James Remnant
scott at canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/dbus/attachments/20090112/ff22ac41/attachment.pgp