Bug#489260: dfm: auto-update uses close to 100% CPU

View: New views

2 Messages — Rating Filter: Alert me

Bug#489260: dfm: auto-update uses close to 100% CPU

by Tim Chase-11 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Package: dfm
Version: 0.99.9-1+b1
Severity: normal

after launching DFM from my .fluxbox/startup or command-line with

dfm &

CPU usage is fine at this point.

After about 40-45 seconds of almost zero CPU usage, the CPU usage for
DFM rockets up to heavy usage and stays there until the process is
killed. This seems to be related to the "40 second" update/refresh
period set in the DFM configuration. Before upgrading my version of
DFM, refresh happened at 40 seconds with no problems. Since the
upgrade, it has caused the heavy CPU usage. Changing the DFM update
frequency to 0 disables auto-update, and prevents the CPU utilization
from sky-rocketing. However, auto-update now seems to be broken.

I've tried leaving it for 5+ minutes to see if it would solve itself,
but it remains at high usage indefinitely until killed.

Output from top:
--------------------------------------------------
Tasks: 87 total, 2 running, 85 sleeping, 0 stopped, 0 zombie
Cpu(s): 4.1%us, 2.2%sy, 0.0%ni, 93.5%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 305136k total, 258276k used, 46860k free, 4772k buffers
Swap: 289160k total, 204k used, 288956k free, 94280k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18705 tim 20 0 6016 1728 1112 R 88.7 0.6 3:17.83 dfm
--------------------------------------------------

a check of the output of "ps axf" shows that the DFM process has no
child-processes, and is in the "R"unning state:

PID TTY STAT TIME COMMAND
18705 ? R 4:19 /usr/bin/dfm

The high CPU usage is also shown by wmtop which graphically shows DFM
with high CPU utilization.

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages dfm depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libglib1.2ldbl 1.2.10-19 The GLib library of C routines
ii libgtk1.2 1.2.10-18.1 The GIMP Toolkit set of widgets fo
ii libx11-6 2:1.1.4-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxi6 2:1.1.3-1 X11 Input extension library
ii libxpm4 1:3.5.7-1 X11 pixmap library
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

dfm recommends no packages.

-- no debconf information

--
To UNSUBSCRIBE, email to debian-qa-packages-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Bug#489260: marked as done (dfm: auto-update uses close to 100% CPU)

by Debian Bug Tracking System :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Your message dated Sat, 5 Jul 2008 23:44:21 +0100
with message-id <200807052244.m65MiLOl007921@...>
and subject line dfm has been removed from Debian, closing #489260
has caused the Debian Bug report #489260,
regarding dfm: auto-update uses close to 100% CPU
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@...
immediately.)

--
489260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489260
Debian Bug Tracking System
Contact owner@... with problems

Package: dfm
Version: 0.99.9-1+b1
Severity: normal

after launching DFM from my .fluxbox/startup or command-line with

dfm &

CPU usage is fine at this point.

After about 40-45 seconds of almost zero CPU usage, the CPU usage for
DFM rockets up to heavy usage and stays there until the process is
killed. This seems to be related to the "40 second" update/refresh
period set in the DFM configuration. Before upgrading my version of
DFM, refresh happened at 40 seconds with no problems. Since the
upgrade, it has caused the heavy CPU usage. Changing the DFM update
frequency to 0 disables auto-update, and prevents the CPU utilization
from sky-rocketing. However, auto-update now seems to be broken.

I've tried leaving it for 5+ minutes to see if it would solve itself,
but it remains at high usage indefinitely until killed.

Output from top:
--------------------------------------------------
Tasks: 87 total, 2 running, 85 sleeping, 0 stopped, 0 zombie
Cpu(s): 4.1%us, 2.2%sy, 0.0%ni, 93.5%id, 0.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 305136k total, 258276k used, 46860k free, 4772k buffers
Swap: 289160k total, 204k used, 288956k free, 94280k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18705 tim 20 0 6016 1728 1112 R 88.7 0.6 3:17.83 dfm
--------------------------------------------------

a check of the output of "ps axf" shows that the DFM process has no
child-processes, and is in the "R"unning state:

PID TTY STAT TIME COMMAND
18705 ? R 4:19 /usr/bin/dfm

The high CPU usage is also shown by wmtop which graphically shows DFM
with high CPU utilization.

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages dfm depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libglib1.2ldbl 1.2.10-19 The GLib library of C routines
ii libgtk1.2 1.2.10-18.1 The GIMP Toolkit set of widgets fo
ii libx11-6 2:1.1.4-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxi6 2:1.1.3-1 X11 Input extension library
ii libxpm4 1:3.5.7-1 X11 pixmap library
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

dfm recommends no packages.

-- no debconf information

Version: 0.99.9-2+rm

The dfm package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/349205 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org

LightInTheBox - Buy quality products at wholesale price