On August 16, 2002 05:46 pm, Danny Tholen wrote: > It seems that drakconf is eating _a lot_ of recourses when left running > idle for half an hour or so. I might need to add that in all cases I tested > I had opened rpmdrake from drakconf as well. > > I attached an strace of the process after a few min of running, and when it > starts being very slow. The difference seems to be that when it is making > the heavy load, it is continuasly doing something with shared memory and > tries to read unavailable resources. Resource 3 (which often gets the > unavailable) is the gtk.pm > > I thought it might be because of the new perl threading. > > Any clues? > > Danny I have been getting this for about the last couple of weeks. It appears that drakconf eats up CPU cycles while X starts eating up memory. This doesn't happen if I start rpmdrake from the command line. I've watched drakconf, grpmi and kswap literally grab all available CPU resources and make my system totally unusable.
Last night I watched via top, as X slowly increased to about 85 % of available memory, (drakconf was doing its thing to the CPU cycles as well) before I killed drakconf. The memory usage briefly dropped down to a very small (around 9%) percentage and came back up to 50+ %. I logged out of X and back in and found that X behaved properly if I stayed away from drakconf....
