Application: kontact (4.4.3) KDE Platform Version: 4.4.3 (KDE 4.4.3) Qt Version: 4.6.2 Operating System: Linux 2.6.33.7-server-2mnb i686 Distribution: "Mandriva Linux 2010.1" -- Information about the crash: 4GB RAM 686 with 4GB swap; Asked Kontact/KNode to update Usenet headers, then left room. Came back to find Kontact gone and error message in place. KNode is subscribed to approximately three dozen newsgroups, a half dozen of which have over 10K messages. (sci.math is the largest.) This is not the first time this sort of blinking out has occurred, but it is the first time since the kdepim debugging code has been installed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 KNGroup::buildThreads (this=0x915a250, cnt=175, job=0xe300cf8) at /usr/src/debug/kdepim-4.4.3/knode/kngroup.cpp:866 #7 0xad6afc39 in KNGroup::insortNewHeaders (this=0x915a250, list=..., job=0xe300cf8) at /usr/src/debug/kdepim-4.4.3/knode/kngroup.cpp:533 #8 0xad69d80e in KNode::ArticleListJob::slotResult (this=0xe300cf8, _job=0xe44d928) at /usr/src/debug/kdepim-4.4.3/knode/nntpjobs.cpp:189 #9 0xad69e0aa in KNode::ArticleListJob::qt_metacall (this=0xe300cf8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf8ea988) at /usr/src/debug/kdepim-4.4.3/build/knode/nntpjobs.moc:139 #10 0xb6decded in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #11 0xb6dfbc5a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #12 0xb6fdc145 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5 #13 0xb6fdc518 in KJob::emitResult() () from /usr/lib/libkdecore.so.5 #14 0xb56b63bf in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5 #15 0xb56b6532 in KIO::ListJob::slotFinished() () from /usr/lib/libkio.so.5 #16 0xb56ba3bd in KIO::ListJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #17 0xb6decded in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #18 0xb6dfbc5a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #19 0xb5788915 in KIO::SlaveInterface::finished() () from /usr/lib/libkio.so.5 #20 0xb578bf04 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libkio.so.5 #21 0xb5788e2a in KIO::SlaveInterface::dispatch() () from /usr/lib/libkio.so.5 #22 0xb577bbe8 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5 #23 0xb577be24 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #24 0xb6decded in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #25 0xb6dfbc5a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #26 0xb567c215 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5 #27 0xb567e6fa in ?? () from /usr/lib/libkio.so.5 #28 0xb567e847 in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5 #29 0xb6decded in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #30 0xb6df7785 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4 #31 0xb6df892f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #32 0xb6315f1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #33 0xb631cd58 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #34 0xb73624a1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #35 0xb6de7a9e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #36 0xb6dea4a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #37 0xb6dea5fc in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #38 0xb6e14add in ?? () from /usr/lib/libQtCore.so.4 #39 0xb40e3cbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0xb40e79f8 in ?? () from /usr/lib/libglib-2.0.so.0 #41 0xb40e7b9e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #42 0xb6e145c1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #43 0xb63d6bda in ?? () from /usr/lib/libQtGui.so.4 #44 0xb6de60fd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #45 0xb6de6549 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #46 0xb6dea6d0 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #47 0xb6315fc4 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #48 0x0804b206 in main (argc=1, argv=0xbf8eb9f4) at /usr/src/debug/kdepim-4.4.3/kontact/src/main.cpp:218 Reported using DrKonqi
After leaving the computer off last night, I restarted Kontact and received e-mail without incident. I switched to KNode for Usenet articles, sorted newsgroups into alphabetical order, started the retrieval, then clicked on the progress viewer in the lower right. After three to four minutes of retrieval, the entire application blinked out, leaving an error message on-screen, Having just reported the same bug last night, I dismissed the error message, then started Kontact from the menu, switched to KNode, and started the recovery again, leaving newsgroups sorted in increasing order of unread messages, and without clicking on the detailed progress bars. The remaining articles were retrieved without crashing. This is another instance of this same bug.
Kontact, Konsole and Firefox were open -- nothing else with a desktop connection. I retrieved e-mail OK, then switched to KNode to get new Usenet articles. After a couple of minutes working the subscribed newsgroup list, Kontact disappeared and was replaced by the crash error screen. This behavior has occurred several times before, so this is not a random Kontact crash. What I suspect may be the case is that Kontact may be running out of working space, and is not able to gracefully handle its own out-of-memory situation, even in a 4GB RAM, 4GB swap, 686 machine.
[Comment from a bug triager] From bug 257550: -- Information about the crash: I finished reading new e-mail messages in KMail, then clicked on the Usenet icon to retrieve new articles. I clicked on the the header above the newsgroups names to sort them into alphabetical order, then clicked to get articles in all news groups. After a few minutes of downloading, without the progress details showing, all of Kontact suddenly disappeared.
*** Bug 257550 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 257814: -- Information about the crash: This crash report begins with mail collected OK, then a fade-away to the crash handler after a little time of KNode collecting new articles while the article list was sorted by number of unread articles. Not on this usage instance, but the previous one, which did not crash, after the article retrieval process was complete, two of the newsgroups reported article counts of 1 each. Clicking on each newsgroup in succession started a search for more new articles, then reports of nine to ten thousand articles in each group, which likely are the correct, or at least closer to correct, actual article counts.
*** Bug 257814 has been marked as a duplicate of this bug. ***
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Bug in KNode which has reached end of life.