What's causing dbus-daemon to take up over 3GB of RAM?
up vote
0
down vote
favorite
dbus-daemon is consuming a lot of memory on my Debian 9/KDE machine. How can I find out why?
The amount of allocated RAM is not changing anymore: it's stable at well over 3GB. I already tried closing my browser which uses most memory as well as any other applications I had opened (not many). I also tried removing some widgets from my desktop.
I also ran dbus-monitor which outputs:
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.152"
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
string ":1.152"
and skimmed over the thousands of entries in sudo kate /var/log/syslog. But I still don't see what's causing this.
What to look for in syslog? Is there a log that gets enabled once processes exceed e.g. specified resource thresholds? What is causing this memory-usage?
Should I run sudo service dbus restart?
debian logs memory ram d-bus
asked 2 days ago
mYnDstrEAm
71941240
add a comment |
up vote
0
down vote
favorite
dbus-daemon is consuming a lot of memory on my Debian 9/KDE machine. How can I find out why?
The amount of allocated RAM is not changing anymore: it's stable at well over 3GB. I already tried closing my browser which uses most memory as well as any other applications I had opened (not many). I also tried removing some widgets from my desktop.
I also ran dbus-monitor which outputs:
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.152"
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
string ":1.152"
and skimmed over the thousands of entries in sudo kate /var/log/syslog. But I still don't see what's causing this.
What to look for in syslog? Is there a log that gets enabled once processes exceed e.g. specified resource thresholds? What is causing this memory-usage?
Should I run sudo service dbus restart?
debian logs memory ram d-bus
asked 2 days ago
mYnDstrEAm
71941240
You need to clarify which and whosedbus-daemonthis is.
– JdeBP
2 days ago
/usr/bin/dbus-daemon and my username. Or what do you mean? Also it just reduced by around half of the RAM. Otherwise the allocated amount doesn't change.
– mYnDstrEAm
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
dbus-daemon is consuming a lot of memory on my Debian 9/KDE machine. How can I find out why?
The amount of allocated RAM is not changing anymore: it's stable at well over 3GB. I already tried closing my browser which uses most memory as well as any other applications I had opened (not many). I also tried removing some widgets from my desktop.
I also ran dbus-monitor which outputs:
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.152"
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
string ":1.152"
and skimmed over the thousands of entries in sudo kate /var/log/syslog. But I still don't see what's causing this.
What to look for in syslog? Is there a log that gets enabled once processes exceed e.g. specified resource thresholds? What is causing this memory-usage?
Should I run sudo service dbus restart?
debian logs memory ram d-bus
asked 2 days ago
mYnDstrEAm
71941240
dbus-daemon is consuming a lot of memory on my Debian 9/KDE machine. How can I find out why?
The amount of allocated RAM is not changing anymore: it's stable at well over 3GB. I already tried closing my browser which uses most memory as well as any other applications I had opened (not many). I also tried removing some widgets from my desktop.
I also ran dbus-monitor which outputs:
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
string ":1.152"
signal time=.. sender=org.freedesktop.DBus -> destination=:1.152 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
string ":1.152"
and skimmed over the thousands of entries in sudo kate /var/log/syslog. But I still don't see what's causing this.
What to look for in syslog? Is there a log that gets enabled once processes exceed e.g. specified resource thresholds? What is causing this memory-usage?
Should I run sudo service dbus restart?
debian logs memory ram d-bus
debian logs memory ram d-bus
asked 2 days ago
mYnDstrEAm
71941240
asked 2 days ago
mYnDstrEAm
71941240
asked 2 days ago
mYnDstrEAm
71941240
asked 2 days ago
mYnDstrEAm
71941240
asked 2 days ago
mYnDstrEAm
71941240
71941240
You need to clarify which and whosedbus-daemonthis is.
– JdeBP
2 days ago
/usr/bin/dbus-daemon and my username. Or what do you mean? Also it just reduced by around half of the RAM. Otherwise the allocated amount doesn't change.
– mYnDstrEAm
2 days ago
add a comment |
You need to clarify which and whosedbus-daemonthis is.
– JdeBP
2 days ago
/usr/bin/dbus-daemon and my username. Or what do you mean? Also it just reduced by around half of the RAM. Otherwise the allocated amount doesn't change.
– mYnDstrEAm
2 days ago
You need to clarify which and whose
dbus-daemon this is.– JdeBP
2 days ago
You need to clarify which and whose
dbus-daemon this is.– JdeBP
2 days ago
/usr/bin/dbus-daemon and my username. Or what do you mean? Also it just reduced by around half of the RAM. Otherwise the allocated amount doesn't change.
– mYnDstrEAm
2 days ago
/usr/bin/dbus-daemon and my username. Or what do you mean? Also it just reduced by around half of the RAM. Otherwise the allocated amount doesn't change.
– mYnDstrEAm
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
The dbus-deamon is the messenger between applications. It may be that the dbus-deamon is being flooded with chatter between two or more applications on the system, for one reason or another.
- I would close all non-essential apps one at a time while monitoring the resource use.
- The messages between apps may not even be error related, so they may not be reported by the monitor unless you make it more verbose.
- I would then attempt to resart the dbus-deamon only if the above does not bare fruit.
If you find that there is an app/apps that is causing this, I would then try to figure why those apps are behaving that way. You could then look through logs about that/those programs and find the cause.
answered 2 days ago
Michael Prokopec
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The dbus-deamon is the messenger between applications. It may be that the dbus-deamon is being flooded with chatter between two or more applications on the system, for one reason or another.
- I would close all non-essential apps one at a time while monitoring the resource use.
- The messages between apps may not even be error related, so they may not be reported by the monitor unless you make it more verbose.
- I would then attempt to resart the dbus-deamon only if the above does not bare fruit.
If you find that there is an app/apps that is causing this, I would then try to figure why those apps are behaving that way. You could then look through logs about that/those programs and find the cause.
answered 2 days ago
Michael Prokopec
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
The dbus-deamon is the messenger between applications. It may be that the dbus-deamon is being flooded with chatter between two or more applications on the system, for one reason or another.
- I would close all non-essential apps one at a time while monitoring the resource use.
- The messages between apps may not even be error related, so they may not be reported by the monitor unless you make it more verbose.
- I would then attempt to resart the dbus-deamon only if the above does not bare fruit.
If you find that there is an app/apps that is causing this, I would then try to figure why those apps are behaving that way. You could then look through logs about that/those programs and find the cause.
answered 2 days ago
Michael Prokopec
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
up vote
1
down vote
The dbus-deamon is the messenger between applications. It may be that the dbus-deamon is being flooded with chatter between two or more applications on the system, for one reason or another.
- I would close all non-essential apps one at a time while monitoring the resource use.
- The messages between apps may not even be error related, so they may not be reported by the monitor unless you make it more verbose.
- I would then attempt to resart the dbus-deamon only if the above does not bare fruit.
If you find that there is an app/apps that is causing this, I would then try to figure why those apps are behaving that way. You could then look through logs about that/those programs and find the cause.
answered 2 days ago
Michael Prokopec
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The dbus-deamon is the messenger between applications. It may be that the dbus-deamon is being flooded with chatter between two or more applications on the system, for one reason or another.
- I would close all non-essential apps one at a time while monitoring the resource use.
- The messages between apps may not even be error related, so they may not be reported by the monitor unless you make it more verbose.
- I would then attempt to resart the dbus-deamon only if the above does not bare fruit.
If you find that there is an app/apps that is causing this, I would then try to figure why those apps are behaving that way. You could then look through logs about that/those programs and find the cause.
answered 2 days ago
Michael Prokopec
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
Michael Prokopec
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
Michael Prokopec
1738
answered 2 days ago
Michael Prokopec
1738
1738
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Michael Prokopec is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482746%2fwhats-causing-dbus-daemon-to-take-up-over-3gb-of-ram%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You need to clarify which and whose
dbus-daemonthis is.– JdeBP
2 days ago
/usr/bin/dbus-daemon and my username. Or what do you mean? Also it just reduced by around half of the RAM. Otherwise the allocated amount doesn't change.
– mYnDstrEAm
2 days ago