Bug 48376 - kio threads are not being killed
Summary: kio threads are not being killed
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports Linux
: NOR normal
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
: 51418 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-09-27 18:18 UTC by michael
Modified: 2003-03-02 01:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2002-09-27 18:18:03 UTC
Version:            (using KDE KDE 3.0.3)
Installed from:    SuSE RPMs
Compiler:          gcc3.2 SuSE 8.1 
OS:          Linux

kio threads started from konqueror or kmail are not being killed. After few hours working I have roughly 200 open kio_file, kio_http, kio_pop3, kio_ftp,... process running, which slows done the computer. 

I have seen a similiar bug for kio_http: 37662. 

I am using KDE3.0.3 shipped with SuSE-8.1


Michael
Comment 1 michael 2002-09-28 09:07:30 UTC
It seems that the problem is related to kdeinit, because not only the kio-processes are not beeing killed. Also kdeinit konqueror or kdeinit kuickshow or some other kdeinit-processes are not beeing killed. For example there are 11 kdeinit konqueror processes, but I have none konqueror running.   Michael 
Comment 2 michael 2002-09-28 19:56:34 UTC
Sorry it was not for freebsd, instead as it was before stated for SuSE-8.1 
Comment 3 michael 2002-09-29 21:01:26 UTC
Problem is solved by removing all files: tmp/ksocket-* files and ~/.mcop*, 
~/.kde/(socket-wptnb8,tmp-wptnb8), i.e. all files or links to old 
relationships of kde.  
 
Michael 
 
Comment 4 Sharad Ahlawat 2002-11-05 03:24:29 UTC
I would like to add to this report

I am also observing this issue under KDE 3.0.9 (RC1). I did not observe it in 3.0.4

I am using the slackware distribution and the slackware packages for KDE

I have a cron job running to kill kio_ processes periodically.
Comment 5 Osho G 2002-12-02 05:04:30 UTC
I just submitted bug # 51418 (http://bugs.kde.org/show_bug.cgi?id=51418) with similar problems - 
not sure if these two are the same bug. (I came across this bug only after submitting #51418).  
 
In my case, I found that disabling socks support in konqueror makes this problem go away and all 
kio_* processes terminate properly. Can anyone confirm?  
 
thanks, 
Osho 
Comment 6 michael 2002-12-02 08:01:38 UTC
Subject: Re:  kio threads are not being killed

Hi Osho!

> ------- Additional Comments From blah_useless@yahoo.com  2002-12-02 05:04
> ------- I just submitted bug # 51418
> (http://bugs.kde.org/show_bug.cgi?id=51418) with similar problems - not
> sure if these two are the same bug. (I came across this bug only after
> submitting #51418).
>
> In my case, I found that disabling socks support in konqueror makes this
> problem go away and all kio_* processes terminate properly. Can anyone
> confirm?

Yes I can confirm this.

Best regards,

Michael


Comment 7 Alexei Dets 2003-02-07 22:58:17 UTC
I have the same problem with KDE-3.1 - kdeinit:kio_* processes are running forever. 
Disabling of SOCKS support solves the problem. Problem appears with both NEC 
socks and Dante. I've never saw this problem with KDE-3.0.x though... 
May be compiler makes the difference - 3.0.x versions were compiled by gcc-2.96, 3.1 
- by gcc-3.2.1. 
 
Here is the backtrace of "sleeping" kio_pop3 (kdeinit, in fact): 
 
(gdb) bt 
#0  0xffffe002 in ?? () 
#1  0x42029ab5 in exit () from /lib/tls/libc.so.6 
#2  0x4018c7c2 in KIO::SlaveBase::sigsegv_handler(int) () from  
/usr/lib/libkio.so.4 
#3  <signal handler called> 
#4  0x40697e21 in posix_memalign () from /usr/lib/libkdecore.so.4 
#5  0x40697236 in free () from /usr/lib/libkdecore.so.4 
#6  0x40f57703 in operator delete(void*) (ptr=0x0) at  
../../../../libstdc++-v3/libsupc++/del_op.cc:39 
#7  0x40668fa1 in KSocks::stopSocks() () from /usr/lib/libkdecore.so.4 
#8  0x40668e57 in KSocks::~KSocks() () from /usr/lib/libkdecore.so.4 
#9  0x4067dc82 in KAppDCOPInterface::functions() () from  
/usr/lib/libkdecore.so.4 
#10 0x42029d4a in __cxa_finalize () from /lib/tls/libc.so.6 
#11 0x405b9745 in _init () from /usr/lib/libkdecore.so.4 
#12 0x4069b4ae in _fini () from /usr/lib/libkdecore.so.4 
#13 0x4000b7d4 in _dl_fini () from /lib/ld-linux.so.2 
#14 0x42029a92 in exit () from /lib/tls/libc.so.6 
#15 0x0804cb2b in strcpy () 
#16 0x0804d7bb in strcpy () 
#17 0x0804dc7c in strcpy () 
#18 0x0804ea59 in strcpy () 
#19 0x420154a0 in __libc_start_main () from /lib/tls/libc.so.6 
 
Comment 8 George Staikos 2003-02-12 03:34:34 UTC
Subject: kdelibs/kdecore

CVS commit by staikos: 


cleanups while trying to hunt #48376

Curiously, does this help?  The problem is very strange.  Does it segfault,
or does it freeze inside posix_memalign()?

CCMAIL: 48376@bugs.kde.org


  M +127 -129  ksocks.cpp   1.23
  M +1 -1      ksocks.h   1.12



Comment 9 George Staikos 2003-02-15 17:59:09 UTC
*** Bug 51418 has been marked as a duplicate of this bug. ***
Comment 10 George Staikos 2003-03-02 01:35:20 UTC
Please provide some feedback or I'll have to close this as 'worksforme'. 
 
Thanks 
Comment 12 George Staikos 2003-03-02 01:48:38 UTC
Good enough for me. :-)  I'll consider this closed.  Thanks Maksim.