http://qa.mandrakesoft.com/show_bug.cgi?id=2873
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 11:59 -------
tested and it's definitely better. Now it's takes about a minute to start using up cpu
resources
totally (according to gkrellm), but mouse responsiveness took a hit immediately after
starting
the program.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
I don't know how else to put this, it eats cpu cycles/uses up all the cpu processing
power.
Whatever the technical term whenever i use logdrake cpu usage goes from around 15 to
99-100 %. The first time it happened i'd selected logdrake from mcc, checked the
"syslog" box
and the "show only for selected day" box (which was today) and then hit search.
IMMEDIATELY cpu usage went up to 100% and the only thing I could do was move the mouse
sporadically. during this sporadic mouse movement i had click on the menu's K icon and
had
move the gkrellm window to somewhere else. After about 5 minutes (yeah I waited that
long)
The search in logdrake finished, the gkrellm window AND the kicker died. The logdrake
window must have died too (as opposed to finishing) because no results were given, it
just
went back to the "System" tab of MCC. This was done in embedded mode. Oh yeah I also
had
a konqueror window open as well. Then I tried to reproduce this:
i restarted kicker and gkrellm using the Alt+F2 run dialog.
clicked on logdrake again in mcc
chose the same seettings ("syslog" and "show only for selected day" boxes) and then
hit search
again.
Same thing happened but this time it was worse. Around the five minute mark all signs
of
activity stopped and I couldn't move the mouse for about thirty seconds, then i could
move the
mouse again. I decided to let it go further and see if it would stop (segfault?) like
it did the
last time. No such luck. It kept going for another five minutes (total of ten) eating
up cpu
usage and I decided to restart X. That in and of itself was an ordeal. It took forever
(probably
a minute) for the Nvidia logo to pop-up and then kdm was STILL trying to restart. So
then I
did Ctrl+Alt+F1 and went to the console (which looked weird too, it was like a tiled
wallpaper across the top with a black screen below) and di a Ctrl+Alt+Del to reboot.
If you
try to reproduce this be prepared.
Oh yeah this was an on upgrade to my regular system (9.0 --> 9.1 RC2+cooker updates)
Specs:
athlon xp 2000+
ecs mobo
gf 4 ti4200-8x
256 mb sdram
p.s. this is a dupe of Bug#: 2161 but I couldn't confirm or change severity and crap
like that
so I made this one wis way better description.
