runaway memory with dbus-daemon --session
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
runaway memory with dbus-daemon --session
My system was running slow earlier today. Checking the system monitor I found that the dbus-daemon process noted above was using 502.9MB of memory! Not knowing how else to correct this, I closed out all my applications and restarted my system. After the restart this process is using 1.6MB of memory.
Has anyone else seen this problem?
Is there a way to cleanly restart this process short of a full system shutdown/restart?
Dave
Has anyone else seen this problem?
Is there a way to cleanly restart this process short of a full system shutdown/restart?
Dave
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
- Larry78723
- Level 14
- Posts: 5479
- Joined: Wed Jan 09, 2019 7:01 pm
- Location: Jasper County, SC, USA
Re: runaway memory with dbus-daemon --session
Without some technical information, we can’t help you. Please post an
Here is how to generate the report and post it:
Open a terminal window (Ctrl-Alt-t). Make it fullscreen to avoid unneeded linebreaks or chopped lines. Execute the command
exactly as it has been typed here.
Mark the complete text output which the command will display with your mouse.
Press the keyboard shortcut <Shift><Ctrl>C to copy the marked text into the clipboard.
Enclose the results between the code markers by selecting </> from the mini toolbar above the textbox where you type your reply then paste <Ctrl>V them in your reply between the code markers
The results will help us to help you.
inxi -Fxxxzr
report. This will give us a concise overview of your hardware and how Mint sees it. Here is how to generate the report and post it:
Open a terminal window (Ctrl-Alt-t). Make it fullscreen to avoid unneeded linebreaks or chopped lines. Execute the command
Code: Select all
inxi -Fxxxzr
Mark the complete text output which the command will display with your mouse.
Press the keyboard shortcut <Shift><Ctrl>C to copy the marked text into the clipboard.
Enclose the results between the code markers by selecting </> from the mini toolbar above the textbox where you type your reply then paste <Ctrl>V them in your reply between the code markers
[code]
Results [/code]
. The results will help us to help you.
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
Re: runaway memory with dbus-daemon --session
Per your request:Larry78723 wrote: ⤴Mon Jul 26, 2021 4:25 pm Without some technical information, we can’t help you. Please post aninxi -Fxxxzr
report. This will give us a concise overview of your hardware and how Mint sees it.
Code: Select all
dhdurgee@z560:~/Downloads$ inxi -Fxxxzr
System: Kernel: 5.4.0-80-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1
dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
Machine: Type: Laptop System: LENOVO product: 0914 v: Ideapad Z560 serial: <filter>
Mobo: LENOVO model: N/A serial: <filter> BIOS: LENOVO v: 29CN40WW(V2.17) date: 04/13/2011
Battery: ID-1: BAT1 charge: 36.7 Wh condition: 49.0/47.5 Wh (103%) volts: 11.2/11.1 model: LG PABAS024 type: Li-ion
serial: <filter> status: Unknown
CPU: Topology: Dual Core model: Intel Core i5 M 480 bits: 64 type: MT MCP arch: Nehalem rev: 5 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21279
Speed: 1206 MHz min/max: 1199/2667 MHz boost: enabled Core speeds (MHz): 1: 1386 2: 1370 3: 1365 4: 1437
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0046
Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz, 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.2.6 direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 00:1b.0 chip ID: 8086:3b56
Sound Server: ALSA v: k5.4.0-80-generic
Network: Device-1: Broadcom and subsidiaries BCM4313 802.11bgn Wireless Network Adapter driver: wl v: kernel port: 5000
bus ID: 05:00.0 chip ID: 14e4:4727
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Lenovo driver: r8169 v: kernel port: 2000
bus ID: 06:00.0 chip ID: 10ec:8136
IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 465.76 GiB used: 61.11 GiB (13.1%)
ID-1: /dev/sda vendor: PNY model: CS900 500GB SSD size: 465.76 GiB speed: 3.0 Gb/s serial: <filter> rev: 0Y13
scheme: MBR
Partition: ID-1: / size: 19.92 GiB used: 11.32 GiB (56.8%) fs: jfs dev: /dev/sda13
ID-2: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda9
Sensors: System Temperatures: cpu: 78.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
1: deb http://silk.apana.org.au/debian stretch main stable-dev unstable-dev
2: deb http://downloads.sourceforge.net/project/ubuntuzilla/mozilla/apt all main
3: deb file:/srv/local/packages/local-focal ./
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://mirrors.advancedhosters.com/linuxmint/packages ulyssa main upstream import backport
2: deb http://mirrors.wikimedia.org/ubuntu focal main restricted universe multiverse
3: deb http://mirrors.wikimedia.org/ubuntu focal-updates main restricted universe multiverse
4: deb http://mirrors.wikimedia.org/ubuntu focal-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http://archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info: Processes: 211 Uptime: 3h 05m Memory: 7.58 GiB used: 1.81 GiB (23.8%) Init: systemd v: 245 runlevel: 5 Compilers:
gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38
dhdurgee@z560:~/Downloads$
Dave
- Larry78723
- Level 14
- Posts: 5479
- Joined: Wed Jan 09, 2019 7:01 pm
- Location: Jasper County, SC, USA
Re: runaway memory with dbus-daemon --session
I don't see a problem. Using 1.8Gb of RAM is normal after being up for 3 hours.
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
Re: runaway memory with dbus-daemon --session
There is no problem at present. The problem occurred about four hours ago. As I noted in the original post, my system was running slow at that point and the system monitor showed the process in the title using over 500MB of memory. I restarted the system and that was reduced to 1.6MB. Even now after four hours of operation it is only using 1.7MB of memory.Larry78723 wrote: ⤴Mon Jul 26, 2021 5:23 pm I don't see a problem. Using 1.8Gb of RAM is normal after being up for 3 hours.
My question is how do I handle this if it occurs again? Looking a bit more at the system monitor data I believe that logging out and back in would also have worked, but once again that involves shutting down all my work to do so. I would hope there is a less drastic way to handle this.
I have no idea what caused the runaway memory usage. Of course I never found out why I was having runaway memory problems with cinnamon either, but I did find an effective way to deal with them. I am hopeful that a similar method is available for this problem.
Dave
- Larry78723
- Level 14
- Posts: 5479
- Joined: Wed Jan 09, 2019 7:01 pm
- Location: Jasper County, SC, USA
Re: runaway memory with dbus-daemon --session
LM20 has fixed several of the memory leaks found in earlier versions however, if you find your machine is suddenly feeling sluggish, you can restart Cinnamon without losing your work by pressing alt+F2, then r then press enter.dhdurgee wrote: ⤴Mon Jul 26, 2021 5:36 pm I have no idea what caused the runaway memory usage. Of course I never found out why I was having runaway memory problems with cinnamon either, but I did find an effective way to deal with them. I am hopeful that a similar method is available for this problem.
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
Re: runaway memory with dbus-daemon --session
Yes, but how can I deal with a problem with the dbus-daemon if it occurs again? I have automated my solution to the cinnamon problem. At this point the only solution I have for the dbus-daemon problem is to stop everything and logout and back in.Larry78723 wrote: ⤴Mon Jul 26, 2021 5:59 pmLM20 has fixed several of the memory leaks found in earlier versions however, if you find your machine is suddenly feeling sluggish, you can restart Cinnamon without losing your work by pressing alt+F2, then r then press enter.dhdurgee wrote: ⤴Mon Jul 26, 2021 5:36 pm I have no idea what caused the runaway memory usage. Of course I never found out why I was having runaway memory problems with cinnamon either, but I did find an effective way to deal with them. I am hopeful that a similar method is available for this problem.
Dave
Re: runaway memory with dbus-daemon --session
After receiving no further guidance here regarding this issue I posted a query to the dbus mailing list. I received clarification of the problem there and unfortunately received confirmation that nothing short of logging out of all sessions will clear this problem.
Dave
Dave
Re: runaway memory with dbus-daemon --session
Attached please find my archived syslog from the time of the problem. I didn't see anything in it myself. You can see the shutdown and restart around 13:36-13:59 in the log.
The response I received on the dbus mailing list is here:
https://lists.freedesktop.org/archives/ ... 18035.html
If another log would be helpful let me know.
Dave
The response I received on the dbus mailing list is here:
https://lists.freedesktop.org/archives/ ... 18035.html
If another log would be helpful let me know.
Dave
- Attachments
-
- syslog.4.gz
- (43.51 KiB) Downloaded 6 times
- Larry78723
- Level 14
- Posts: 5479
- Joined: Wed Jan 09, 2019 7:01 pm
- Location: Jasper County, SC, USA
Re: runaway memory with dbus-daemon --session
Earlier in the log you have multiple instances of the following:
I'm not the person to examine this, but I don't know if this was caused by the dbus problem or the other way around but feel it is worth investigating.
Code: Select all
Jul 26 13:44:18 Z560 kernel: [492106.172875] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 9054)
Jul 26 13:44:18 Z560 kernel: [492106.172877] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 9054)
Jul 26 13:44:18 Z560 kernel: [492106.173901] mce: CPU2: Core temperature/speed normal
Jul 26 13:44:18 Z560 kernel: [492106.173902] mce: CPU3: Core temperature/speed normal
Jul 26 13:49:27 Z560 kernel: [492414.677197] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 9388)
Jul 26 13:49:27 Z560 kernel: [492414.677198] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 9388)
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
Re: runaway memory with dbus-daemon --session
Taking a look at my current and last archived syslog I see over 200 lines of this type since 20:00 yesterday. Despite this the dbus-daemon --session process is using only 12.8Mb, which while greater than when it started is far from a runaway. Given this I doubt this is the cause of the problem.Larry78723 wrote: ⤴Fri Jul 30, 2021 10:18 am Earlier in the log you have multiple instances of the following:I'm not the person to examine this, but I don't know if this was caused by the dbus problem or the other way around but feel it is worth investigating.Code: Select all
Jul 26 13:44:18 Z560 kernel: [492106.172875] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 9054) Jul 26 13:44:18 Z560 kernel: [492106.172877] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 9054) Jul 26 13:44:18 Z560 kernel: [492106.173901] mce: CPU2: Core temperature/speed normal Jul 26 13:44:18 Z560 kernel: [492106.173902] mce: CPU3: Core temperature/speed normal Jul 26 13:49:27 Z560 kernel: [492414.677197] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 9388) Jul 26 13:49:27 Z560 kernel: [492414.677198] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 9388)
Dave