| Summary: | System Load Viewer Loses Memory Completely Every Few Seconds | ||
|---|---|---|---|
| Product: | [Applications] ksysguard | Reporter: | Garry Williams <gtwilliams> |
| Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | aseigo |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | not-gone*.png shows normal display gone*.png shows missing memory | ||
Upgraded to F15 and this bug persists. Actually all of the monitored resources "disappear" intermittently -- CPU, memory, and swap. I also observe that plasma-desktop will eventually consume 100% CPU and ksysguard is always right below it in top, too. Killing ksysguard gets things back to normal for a while, but eventually, the same thing happens: plasma-desktop uses 100% CPU. kdebase-4.6.3-2.fc15.x86_64 kdebase-libs-4.6.3-2.fc15.x86_64 kdebase-runtime-libs-4.6.3-1.fc15.x86_64 kdeplasma-addons-libs-4.6.3-1.fc15.x86_64 kdebase-workspace-4.6.3-8.fc15.x86_64 kdebase-workspace-libs-4.6.3-8.fc15.x86_64 I think this was a btrfs problem. Sometimes the system was totally unresponsive for several seconds. Unusually high I/O accompanied this symptom. A top display showed btrfs-endio-wri at the top with a few percent CPU. Very high I/O wait percentages were displayed. Running vmstat didn't show any unusual write or read rates, though. Anyway, the problem goes away since I updated my kernel to 2.6.38.7-30.fc15.x86_64. |
Created attachment 59789 [details] not-gone*.png shows normal display gone*.png shows missing memory Version: unspecified (using Devel) OS: Linux The system load viewer widget reports 0% usage on 0 MiB of memory every few seconds. Reproducible: Always Steps to Reproduce: Log in Observe system load viewer in panel Actual Results: Memory usage disappears every few seconds. Expected Results: Memory usage should continuously display usage. My system is kde 4.6.3 from Fedora updates-testing but I observed this bug on 4.6.2, also.