Version: (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages The progress window on the right of the status bar is responsable together with Xorg for a CPU-load of 100% (continuously) on a lower end machine. The moment I change focus to another window making knode inactive and invisible, the load drops immediately. So I can surely say it is indeed this progress window (probably the moving bar) which is hungry for CPU-cycles.
I do not see what you are describing, so : - What is a lower end machine ? - Is knode running standalone or embedded inside kontact ? - Do you encounter this behaviour each time you use knode ? - Is there a special suite of actions that leads to this cpu load ? - how much accounts/newsgroups are you subscribed to ? Is there any other special things that could explains/allow to reproduce this load ?
1. A PIII-500 with 512MB RAM 2. standalone 3. every time (when the progress window (well, the thing that moves from left to right and back) on the right side of the status bar is visible) When I hide the status bar, or I make the window invisible by minimizing it, or changing to another virtual desktop, the load drops immediately. 4. Not that I know off. If you click on the button just left of it, then you can see the actions what Knode is waiting for. (connections to close (a few) for example) 5. 2 accounts. 3 in the first and 22 in the other.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.