Indeed. But it seems to be even too much for batterypatch.

Batterypatch uses dbus-scripts, which could (maybe) responsible for the leak.

The scripts run by batterypatch, which are invoked by dbus-scripts, also execute dbus commands (to know whether a call is active or not).

So perhaps this provoke-dbus-event while handle-dbus-event may trigger a bug in dbus itself. (Maybe, this is not really a re-entrancy issue, and in any case one must assume that dbus, however crappy it is, and it is, has to be re-entrant, otherwise it would be just way too crappy).

Is somebody using frequently-run dbus-activated scripts *and* also having this memory leak?

If so, is this using dbus-scripts, dbuscron, or some other means?