Version: (using KDE 4.2.3) OS: Linux Installed from: Unlisted Binary Package I caught kio_sieve eating 100% cpu for an extended period. Unfortunately I dno not know how to reproduce, and I do not have debugging packages installed. I got a strace showing it's stating /etc/localtime as fast as possible. Tens of thousands of lines of: stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1649, ...}) = 0 The backtrace indicates this might be a Qt bug. I'm not sure, however. I'm hoping knowing the call stack and strace line might be enough to find out what's happening: #0 0xffffffffff6001a7 in ?? () #1 0x00007fff913ff542 in ?? () #2 0x00007fff913ff5d6 in gettimeofday () #3 0x00007f74863f5caa in gettimeofday () from /lib/libc.so.6 #4 0x00007f7488ce6cc0 in QTime::currentTime () from /usr/lib/libQtCore.so.4 #5 0x00007f7488ce6da9 in QTime::start () from /usr/lib/libQtCore.so.4 #6 0x00007f74851877f8 in QSslSocket::waitForReadyRead () from /usr/lib/libQtNetwork.so.4 #7 0x00007f7487d67bd2 in KIO::TCPSlaveBase::readLine () from /usr/lib/libkio.so.5 #8 0x00007f748077acbe in kio_sieveProtocol::receiveData () from /usr/lib/kde4/kio_sieve.so #9 0x00007f748077b11b in kio_sieveProtocol::operationSuccessful () from /usr/lib/kde4/kio_sieve.so #10 0x00007f748077ac41 in kio_sieveProtocol::disconnect () from /usr/lib/kde4/kio_sieve.so #11 0x00007f7487d59f1e in KIO::SlaveBase::dispatchLoop () from /usr/lib/libkio.so.5 #12 0x00007f748077bc91 in kdemain () from /usr/lib/kde4/kio_sieve.so #13 0x0000000000406b1c in _start ()
Looks related to bug 186455.
*** This bug has been marked as a duplicate of bug 186455 ***