Bug 135147
Summary: | Excessive swap and cpu usage when system-logviewer loads | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew Farris <lordmorgul> | ||||
Component: | system-logviewer | Assignee: | Chris Lumens <clumens> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-04-21 20:42:24 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Andrew Farris
2004-10-09 01:44:59 UTC
Created attachment 104967 [details]
backtrace of python running system-logviewer
This backtrace is not taken while the system is fully hung, I cannot bring it to a complete hang state, but the backtrace does change at different times while continuing under gdb. It has been deeper, into xft calls but this so if this is not very helpful I'd appreciate hints how to recover something that will help more. I am new to fairly new to gdb. What is your refresh time set too in Preferences? Which log are you viewing when this occurs. What is the actuall log file size: ls -al /var/log/ Please could you show the memory usage via vmstat or top for system-logviewer. For more detailed X resource usage can you do (yum install xrestop): xrestop -b | grep -A 14 system-logviewer Whilst memory use is high. I apologize for the delay in getting back to this one. I had the requested output but cannot find it.. and cannot reproduce the behavior anymore. I will make another attempt to push the program and see what happens, but (see below) I think this may have been a problem "between chair and keyboard". It is a shame Bugzilla doesn't have a resolution to fit that. What I did find out was that I had one messages logfile (I think it was rotated and gzip'd but not positive now) that was 90+ Mb of runaway selinux spam. The refresh being used was default, which appears to be 30secs. That might create an unreasonable load on parsing the logs. Perhaps logs of 'larger' size should not refresh, although the initial load would still take a long time. If this was simply a problem of my one large logfile it made the system unusable while the process was still running, and that should be avoided if possible. system-logviewer has been removed from core. |