_dbus_get_oom_wait magic
Havoc Pennington
hp at redhat.com
Wed Jul 27 03:56:58 EST 2005
On Tue, 2005-07-26 at 19:44 +0200, Timo Hoenig wrote:
>
> whenever I dare to run several turns of
>
> * establish a connection
> * send a message (signal or method call) to the bus
> * close the connection
>
> within short intervals, latter turns are really slow (roughly more than
> 500ms).
>
> While debugging it turned out that the invocation of
> dbus_connection_dispatch() in _dbus_loop_dispatch returns
> DBUS_DISPATCH_NEED_MEMORY. Thus, _dbus_wait_for_memory and
> _dbus_wait_for_memory get invoked which leads to the delay of 500ms.
>
> Now, since my system does not run out of memory, I am wondering if there
> is some bug in the dbus_connection_dispatch routine which I am not
> able to understand to its full extend.
Sounds likely; NEED_MEMORY should only happen if there's no memory... I
don't know of a bug like this though. The way to debug is to look at the
verbose log.
Havoc
More information about the dbus
mailing list