_dbus_get_oom_wait magic

[Timo Hoenig]

Hi,

On Wed, 2005-07-27 at 09:49 -0400, Havoc Pennington wrote:

> The next thing I'd do is start adding verbose debug spew everywhere that
> NEED_MEMORY gets returned from connection_dispatch()
> 
> That should let you know the next stack frame (where in
> connection_dispatch() it failed) and then you can add verbose printouts
> everywhere that OOM happens in the next function down, and so forth
> until you get to what actually happens.
> 
> I thought I had verbose spew in most places that return OOM but
> obviously not.

My previous analysis of the problem was wrong, sorry.  The actual delay
of the test runs where due to a invocation of  _dbus_wait_for_memory ()
in bus_connection_disconnected ().

The attached patch fixes the problem. Please review.

> Havoc

See you,

   Timo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dbus-transaction_fix.patch
Type: text/x-patch
Size: 398 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/dbus/attachments/20050803/a5639054/dbus-transaction_fix.bin