Ubuntu
iotop package

iotop uses 100% cpu time

Bug #1156754 reported by Kyle Bentley
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
iotop (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I've noticed a trend lately that whenever I use iotop, and close the terminal instead of quitting, that the cpu utilization reaches 100%, and stays there. I have to kill the pid before it settles down.

I'm using xubuntu 12.10x64 fully updated,

To reproduce:
open terminal
sudo iotop
close terminal
open new terminal
top
sort by cpu usage with 'c'
notice that iotop is munching on cpu.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: iotop 0.4.4-4
ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Mon Mar 18 13:23:12 2013
InstallationDate: Installed on 2013-02-01 (45 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
SourcePackage: iotop
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kyle Bentley (kwbent) wrote :
Revision history for this message
Paul Wise (Debian) (pabs) wrote : iotop: 1156754: fixed in git

I've created a fix for this issue and forwarded it to the upstream
maintainer, thanks for the report.

 status inprogress

--
bye,
pabs

http://wiki.debian.org/PaulWise

Changed in iotop (Ubuntu):
status: New → In Progress
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "0003-Exit-when-a-SIGTERM-signal-is-received-in-interactiv.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package iotop - 0.5-2

---------------
iotop (0.5-2) unstable; urgency=low

  * Upload to unstable now that wheezy is out
  * Fix the FSF address in the copyright information
  * Fix a Python 3 incompatibility issue
  * Exit when a SIGTERM signal is received in interactive mode. (LP: #1156754)

 -- Paul Wise <email address hidden> Mon, 06 May 2013 13:25:07 +0800

Changed in iotop (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.