I have run across an interesting problem in SuSE8.1... not sure how to properly fix it. I am doing some web development using Quanta (the version provided on the SuSE8.1 disks). After working on various pages over several hours, I noticed my CPU load was very high, and system response was getting worse and worse. I figured the kernel was off doing some housekeeping and stopped working for a while. Came back, and CPU load was still maxed out. I messed around with process IDs and killing a few here and there to see if it made a difference. I ended up restarting to see how that affected things. Hmmm CPU load back to zero. I went back to work in Quanta, and within a couple hours the same thing again. After sitting idle to 6 hours *overnight) top reports this: ------------------------------------------------------------------------------ 104 processes: 83 sleeping, 21 running, 0 zombie, 0 stopped CPU states: 18.0% user, 81.9% system, 0.0% nice, 0.0% idle Mem: 709320K av, 686880K used, 22440K free, 0K shrd, 59600K buff Swap: 1052248K av, 3480K used, 1048768K free 455888K cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND 2276 ccornell 25 0 15292 12M 10348 R 17.8 1.7 115:57 kdeinit 2344 ccornell 25 0 19288 16M 10984 R 17.8 2.3 110:16 kdeinit 2665 ccornell 25 0 14884 11M 10348 R 17.6 1.7 85:18 kdeinit 2218 ccornell 25 0 15352 12M 10348 R 14.9 1.7 129:52 kdeinit 2776 ccornell 25 0 15648 12M 10960 R 14.9 1.8 76:25 kdeinit 2858 ccornell 25 0 13704 10M 9580 R 14.9 1.5 74:06 kdeinit ------------------------------------------------------------------------------ I cannot kill (either in top, or in a terminal with -9 option) the kdeinit processes, and they will not stop doing whatever it is they are doing. CPU load for system ranges from 80% to 100%. I could logout/restart to clean up.. but I would rather undertand what is going on here. Anyone have any ideas why this is happening? Anyone else experience this? C.
Clayton Cornell <c.cornell@chello.nl> observed ~
CPU load was very high, and system response was getting worse and worse
~ maybe X / kdeinit got the bit between the teeth. ~ closing your window-manager/GUI , and, re-starting it, should fix it. Seems Konq sometimes does this to me :) -- best wishes ____________ sent on Linux ____________
On Friday 15 November 2002 08:23, tabanna wrote:
Clayton Cornell <c.cornell@chello.nl> observed ~
CPU load was very high, and system response was getting worse and worse
~ maybe X / kdeinit got the bit between the teeth.
~ closing your window-manager/GUI , and, re-starting it, should fix it.
Seems Konq sometimes does this to me :)
Yah, logging out of KDE cleaned things up. I'm just puzzled.... wondering if anyone else is experiencing the same when using Quanta. I quite like Quanta and have been using it for a long time now... it seems that if I use it for a couple hours things jam up and kdeinits go crazy. I hate having to log out and back in again every 2 hours or so just so I can keep working.... Hmmmm I'll keep poking around I guess. C.
On Friday 15 November 2002 09:30 am, Clayton Cornell wrote:
On Friday 15 November 2002 08:23, tabanna wrote:
Clayton Cornell <c.cornell@chello.nl> observed ~
CPU load was very high, and system response was getting worse and worse
______________
~ maybe X / kdeinit got the bit between the teeth.
~ closing your window-manager/GUI , and, re-starting it, should fix it.
Seems Konq sometimes does this to me :)
Yah, logging out of KDE cleaned things up. I'm just puzzled.... wondering if anyone else is experiencing the same when using Quanta. I quite like Quanta and have been using it for a long time now... it seems that if I use it for a couple hours things jam up and kdeinits go crazy. I hate having to log out and back in again every 2 hours or so just so I can keep working.... Hmmmm I'll keep poking around I guess.
C. ================== Clayton, If you want to see which processes are causing your most cpu usage, then while in TOP use these keystrokes to get more information.
shift-p or P will put those cpu intensive processes at the top shift-m or M will put the memory intensive processes at the top just "c" will put a name to each process telling you what the actual process is connected to that kdeinit. That may help you trace down the offending processes and work out a cure for the cpu illness! ;o) Patrick -- --- KMail v1.4.3 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206
CPU load was very high, and system response was getting worse and worse wondering if anyone else is experiencing the same when using Quanta. I quite like Quanta and have been using it for a long time now... it seems that if I use it for a couple hours things jam up and kdeinits go crazy. I hate having to log out and back in again every 2 hours or so just so I can keep working.... Hmmmm I'll keep poking around I guess. If you want to see which processes are causing your most cpu usage, then while in TOP use these keystrokes to get more information.
shift-p or P will put those cpu intensive processes at the top shift-m or M will put the memory intensive processes at the top just "c" will put a name to each process telling you what the actual process is connected to that kdeinit.
Ok... got around to working in Quanta again this morning. Within 20 minutes CPU load was close to 100%. Top gives me this interesting bit of info.... ------------------------------------------------------- 16169 ccornell 25 0 18392 15M 11132 R 98.4 2.2 24:10 kdeinit: kio_thumbnail thumbnail /tmp ------------------------------------------------------- PID 16168 is eating up 98.4% of the CPU. I can kill the process... eventually. Takes a bit of fiddling to make it go away, but it eventually accepts it's fate and dies. Seems to be tied to the preview pane when you open an existing HTML file and Quanta generates a thumbnail. Don't kow why this is causing problems though. Hmmm more digging.. C.
participants (3)
-
Clayton Cornell -
Patrick -
tabanna