Version: unknown (using KDE 3.1.0 (KDE 3.1 RC4)) Installed from: compiled sources Compiler: gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) OS: Linux (i686) release 2.4.18-14 Hi, I am currently using KDE 3.1 (RC4) and noticed that none of kioslaves (kio_* processes) ever terminate. Pretty soon (say after an hour of browsing), I have ~100 kio_http, kio_file, kio_ftp, kio_help etc. processes all consuming system resources and everything starts getting really slow. I can not kill any of them by 'kill pid' - I have to use 'kill -9 pid'. I had the same problem with KDE 3.1 beta 2 as well. By trial and error, I found that if I disable socks support in konqueror, this problem goe away and kio_* processes terminate properly. I have no clue how these two are related. To ensure that these two are indeed related, I created a kdetest user and set up KDE with all default KDE settings and did a small experiment. All kio_* processes terminate normally with KDE/Konqueror's default settings. If I enable socks in Konqueror - none of the kio_* processes terminate. I have to use 'kill -9' to terminate them. Any ideas? thanks, Osho
Please see the discussion and mention of this bug in bug# 48376. I guess developer(s) can confirm that this is indeed the same bug and then mark it as such. Disabling socks support in konqueror seems to be (possibly questionable) the work around. thanks, Osho
*** This bug has been marked as a duplicate of 48376 ***