| Summary: | ksysguard counts up to thousands of CPU usage percentage for the init process | ||
|---|---|---|---|
| Product: | [Applications] ksysguard | Reporter: | Daniele Cocca <daniele.cocca> |
| Component: | ksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jessie |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Chakra | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Live screenshot of the ksysguard fail. | ||
I too am having this issue. I'm on Kubuntu 11.04 using 4.8 RC2 from one of the PPA's. I have to agree, it does appear to be adding up the CPU usage rather than replacing. Could someone mark this as confirmed? *** This bug has been marked as a duplicate of bug 290687 *** |
Created attachment 68038 [details] Live screenshot of the ksysguard fail. Version: unspecified (using Devel) OS: Linux When I fire up ksysguard and choose the "process tree" view, I can see the CPU usage percentage for the init process is a normal one, usually not more than 30%-40%, but if I leave ksysguard open, it easily goes up to several thousands of percentage. I'm attaching a screenshot that shows this behavior. Reproducible: Always Steps to Reproduce: Open ksysguard, select process tree view, order by CPU usage, leave it open for a couple of minutes. Actual Results: Thousands of CPU usage percentage reported. Attached screenshot shows more than 10000%. Expected Results: Actual CPU usage is shown. From a quick look, it seems like at each step the new CPU usage percentage is added to the old one, instead of simply replacing it.