Bug 129629 - Top fails to show CPU hog
Top fails to show CPU hog
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: procps (Show other bugs)
2
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Karel Zak
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-08-10 23:22 EDT by Sam Williams
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-07 05:27:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Williams 2004-08-10 23:22:03 EDT
Description of problem:
I have been using an RSS aggregator called liferea. Its built with
python. Occasionally, it will go out to lunch and start consuming
large quantities of cpu. Gkrellm and the CPU panel app show the
utilization going up. If I use the top command I see what looks to be
an unused system. It doesn't register what the other utilities see. It
looks like a very quiet and unused system.


Version-Release number of selected component (if applicable):
top uses procps version 3.2.0

How reproducible:
When it dies its consistent. Haven't figure out how to cause liferea
to break. So far this is the only program that demonstrates this
inability. 

Steps to Reproduce:
1. Fire up liferea
2. Wait til CPU starts going up 
3. pop open top
  
Actual results:
Top doesn't register the liferea process consuming all the cpu.

Expected results:
To see the top process being liferea or python, since liferea is
python code. But I see neither


Additional info:
Comment 1 Rik van Riel 2004-09-27 17:48:21 EDT
Does liferea use threads ?

If you switch on display of all threads in top, do things work the way
they should ?
Comment 2 Albert Cahalan 2004-10-23 12:57:22 EDT
should be fixed with the 2.6.10 kernel

Note You need to log in before you can comment on or make changes to this bug.