Summary: | Kontact aborts while retrieving Usenet headers [KNGroup::buildThreads, KNGroup::insortNewHeaders, KNode::ArticleListJob::slotResult] | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | kmmos1 |
Component: | news | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | andresbajotierra, kmmos1, nive |
Priority: | NOR | ||
Version: | 4.4.3 | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
kmmos1
2010-11-18 10:34:40 UTC
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. |