| Summary: | pop mail transfer hangs (sporadic) | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Mike Durian <durian> |
| Component: | pop3 | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | normal | CC: | andrey, bjoern, juuso.alasuutari, leva, lofi |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Mike Durian
2006-02-22 01:26:42 UTC
A few more details. I've discovered kmail is leaving a number of kio_pop3 processes behind when this happens. Perhaps it is normal for kio_pop3 processes to keep running, but if they are supposed to exit when the popping is complete, then this might be related to the problem I am seeing. ps -lw shows they are blocked on the kserel channel. I no longer have the slow sprintbroadband connection, but I'm still seeing the problem with a fast cable connection.
Here is a gdb backtrace from a wedged pop process. I hope the proves useful to someone as this is a very annoying problem.
(gdb) info thread
* 3 LWP 100142 0x294417dd in read () from /lib/libc.so.6
2 Thread 0x805d000 (runnable) 0x294417df in read () from /lib/libc.so.6
1 Thread 0x833fa00 (LWP 100139) 0x2938446b in pthread_testcancel ()
from /usr/lib/libpthread.so.2
(gdb) thread 2
[Switching to thread 2 (Thread 0x805d000 (runnable))]#0 0x294417df in read ()
from /lib/libc.so.6
(gdb) bt
#0 0x294417df in read () from /lib/libc.so.6
#1 0x2936d19a in read () from /usr/lib/libpthread.so.2
#2 0x297409d1 in BIO_sock_should_retry () from /lib/libcrypto.so.4
#3 0x297a93c3 in BIO_read () from /lib/libcrypto.so.4
#4 0x298c8cf9 in SSL_set_msg_callback () from /usr/lib/libssl.so
#5 0x298c9922 in ssl3_read_bytes () from /usr/lib/libssl.so
#6 0x298cb035 in ssl3_renegotiate_check () from /usr/lib/libssl.so
#7 0x298c652e in SSL_read () from /usr/lib/libssl.so
#8 0x2821310c in KOpenSSLProxy::SSL_read (this=0x8363160, ssl=0x83b4400,
buf=0xbfbfd1b0, num=4095) at kopenssl.cc:661
#9 0x28203317 in KSSL::read (this=0x8347a40, buf=0xbfbfd1b0, len=4095)
at kssl.cc:485
#10 0x282677bb in KIO::TCPSlaveBase::read (this=0x8349000, data=0xbfbfd1b0,
len=4095) at tcpslavebase.cpp:174
#11 0x296bd321 in POP3Protocol::myRead () from /usr/local/lib/kde3/kio_pop3.so
#12 0x296c2727 in POP3Protocol::get () from /usr/local/lib/kde3/kio_pop3.so
#13 0x2826b1a1 in KIO::SlaveBase::dispatch (this=0x8349000, command=67,
data=@0xbfbfe320) at slavebase.cpp:1020
#14 0x28269d05 in KIO::SlaveBase::dispatchLoop (this=0x8349000)
at slavebase.cpp:290
#15 0x296bcfe0 in kdemain () from /usr/local/lib/kde3/kio_pop3.so
#16 0x0804f21d in launch (argc=4, _name=0x8345404 "kio_pop3",
args=0x8345486 "", cwd=0x0, envc=0, envs=0x834548a "", reset_env=false,
tty=0x0, avoid_loops=96, startup_id_str=0x805189c "0") at kinit.cpp:639
#17 0x0804f8ca in handle_launcher_request (sock=8) at kinit.cpp:1203
#18 0x0804fe6c in handle_requests (waitForPid=0) at kinit.cpp:1406
#19 0x08050465 in main (argc=2, argv=0xbfbfe980, envp=0xbfbfe98c)
at kinit.cpp:1850
This could be the same as bug 124185. *** Bug 131013 has been marked as a duplicate of this bug. *** *** Bug 124185 has been marked as a duplicate of this bug. *** *** Bug 139630 has been marked as a duplicate of this bug. *** Do you still need to kill kio_pop3 with more recent kmail versions? No, I do not have to kill kio_pop3 anymore. I do often have to exit kontact and restart it when things get wedged, but I don't know if that condition is related to this bug. Sorry, jumped the gun with that last comment. I'm using imap now, not pop3. So, I can't confirm this problem has gone away. But we need infos from someone who does use kio_pop :) |