For some time now, (months, I think), I've been having memory hangs, which mostly spin around dbus-deamon. As far as I learned from other posts and google, dbus starts filling up memory when some other program floods it with messages or something like that (correct me if I am wrong please.)

I figured out today that clementine was clogging up dbus (when clementine is on and running, dbus fills up about 0.05 - 0.1 MB of RAM per second).

Right now, I am at 2 hrs of uptime with dbus-deamon looks like this in a
Code:
ps aux
listing:
catalin 1656 1.0 6.6 161576 128392 ? Ss 14:23 1:15 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

If I stop clementine, memory usage still climbs (though much slower), something else must be hanging it as well.

Can someone explain me how dbus processes messages (or whatever is sent to it)? What happens when it can not process something? Is there any way to clear all the messages stuck in it's queue? (I know nothing of how dbus works internally).

Some other sites suggested I use
Code:
dbus-monitor --session
to figure out what is wrong. A couple seconds of this running can be found here (clementine was closed), however I can't really make heads or tails about that. It doesn't really show anything else (at least not now), but memory usage still goes up.

I really don't know what to do about this, and I appreciate any help.

Thanks.