Bug 74917

Summary: Very High System % and User % Loads on process 'X' after closing window(s)
Product: [Applications] konqueror Reporter: Saad Malik <simfox3>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Saad Malik 2004-02-11 07:17:49 UTC
Version:           3.2.0 (using KDE KDE 3.2.0)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.1 -O3 --march=pentium4
OS:          Linux

Hi,
I just recently upgraded to 3.2.0.... WOW! Nice!

All known bugs I had known from Kde 3.1.4 were vaporized, and some of those deep intimate wishes of mine were introduced... Great..

However, there is a very big bug... atleast for me... 

What happens is that **somtimes** when I open a window (primarily Konqueror), and then close it after what ever I need to do... it ties up the 'X' process indefintely with very high system% (50%) and user %'s (20%). The only way to kill it is to logout and login back in. 

I know that ***sometimes*** isn't good enough for a bug report... so I played around and I have so far been able to reproduce the error 13/13 times:

1. Login to KDE (smile :) )
2. Hit CTRL+Esc, and set it to Always stay on top. 
3. Go crazy on the konsole, home, and konqueror buttons (press them like numerous times random order... have like 10 instances of each or something)
3. Right-click on one group (after it gets grouped... and click close all)
4. Watch how the 'X' system % and user % goes high... and stays high. 

I am using gcc 3.3.1 with -O3 --march=pentium4.... --enable-fast-malloc=full on kdelibs... what else do you need to know?

XFree86 4.3.0 (using the proprietory Nvidia modules)... note however I have tried it with loading the built in nv, and the vesa module and the same result.
Comment 1 Saad Malik 2004-02-11 21:59:40 UTC
Hello...
I did some testing today, .... I removed the whole /opt/kde-3.2.0 folder... and I installed packages one by one, and started opening and closing multiple windows.... I'm not entirely sure, but I think it has to do something with kdeutils-3.2.0 package... the only times 'X' crashes is when that package is installed... Also I noiced that when I took out the power from my laptop while surfing the web... the same thing happened... So it may be something with the laptop daemon in kdeutils. I removed the package, and then tried yanking the power cord, but no problems... I will try to survive without installing kdeutils, for a couple of days and test this configuration... So far the only packages installed: arts, kdelibs, kdebase, kdegraphics. 

I'll post an update tommorow. 

Comment 2 Saad Malik 2004-02-12 21:02:37 UTC
Hello active listners (if any),
I wiped out my whole /opt/kde-3.20 folder again, and got the cvs kde modules... so far I'm running with everything (except kdepim, which refuses to compile). No problems yet....so i'll wait and see.. 

I'll see you guys/gals tommorow! (or before if problems arise). 
Comment 3 Saad Malik 2004-02-12 21:51:03 UTC
I'm back!

Guess what?... 10 minutes after running KDE CVS (with kdeutils) the problem happened again. ... 2 times.....

I removed kdeutils (make uninstall), and no problems yet.. There is something wrong with that package and I'm guessing it is klaptopdaemon.... can someone move this to kdeutils bug?
Comment 4 Saad Malik 2004-02-13 08:23:19 UTC
Good Afternoon Ladies and Gentlemen.... I'm in a good mood :)

Actually very good news... I was googling around out of desperation.. and I came across this one post where another user was having similar problems with the kdepim package... as soon as he installed it that the cpu usage shot up... someone had commented on upgrading to the newest qt.... so I'm like.. why not..

I did it.. took another 5 hours of recompile... and guess what? It looks like it is working... I'm not going to close this report today.. just in anticipation of murphy's law in reacurrance.... i'll close it tommorow if no problems...

Just to let you know.. i had qt 3.2.1 now I have 3.3.0. 
Comment 5 Lubos Lunak 2004-02-13 14:31:21 UTC
Yes, you need at least qt-3.2.3 to fix this problem.


*** This bug has been marked as a duplicate of 64671 ***