Is this bug a recent regression, or have you seen it before?

It's not recent. Remember how I talked with you on IRC about it and then deleted my Archivee/? Since then it didn't happen again so I forgot about it, until now the expiration stuff started to kick in again. :-)

I think commit 495480 fixes this (see also Bug 114997 http://bugs.kde.org/show_bug.cgi?id=114997). Stephan (and everyone else using current CVS), could you report if this still occurs in 3.5 branch >= 495480?

Didn't crash since updating anymore, let us hope it keeps running. :-)

Sadly it just happened again for me, the backtrace including all line numbers is the same.

bt from Bug 121247

"This is on a x86_64"

[Thread debugging using libthread_db enabled] 
 [New Thread 46912598553984 (LWP 6197)] 
 [KCrash handler] 
 #5  0x00002aaaae6fda81 in QListViewItem::takeItem (this=0x194d700, 
     item=0x12a6d60) at qlistview.cpp:1314 
 #6  0x00002aaaae6fcea7 in ~QListViewItem (this=0x12a6d60) at qlistview.cpp:1019 
 #7  0x00002aaaad1023e1 in ~KListViewItem (this=0x12a6d60) at klistview.cpp:2191 
 #8  0x00002aaab0e22b53 in ~ArticleItem (this=0x12a6d60) 
     at articlelistview.cpp:163 
 #9  0x00002aaab0e25183 in Akregator::ArticleListView::slotArticlesRemoved ( 
     this=0x720370, list= at 0x7fffffc7c0f0) at articlelistview.cpp:444 
 #10 0x00002aaab0e256c8 in Akregator::ArticleListView::qt_invoke ( 
     this=0x720370, _id=-3686248, _o=0x7fffffc7c060) at articlelistview.moc:226 
 #11 0x00002aaaae6000bd in QObject::activate_signal (this=0xb206e0, 
     clist=0xb2d510, o=0x7fffffc7c060) at qobject.cpp:2380 
 #12 0x00002aaaaac2f5ff in Akregator::TreeNode::signalArticlesRemoved ( 
     this=0xb206e0, t0=0xb206e0, t1= at 0x7fffffc7c0f0) at treenode.moc:190 
 #13 0x00002aaaaac29e5e in Akregator::Feed::doArticleNotification ( 
     this=0xb206e0) at feed.cpp:795 
 #14 0x00002aaaaac2f1d5 in Akregator::TreeNode::setNotificationMode ( 
     this=0xb206e0, doNotify=true, notifyOccurredChanges=true) 
     at treenode.cpp:133 
 #15 0x00002aaaaac2a3a6 in Akregator::Feed::slotDeleteExpiredArticles ( 
     this=0xb206e0) at feed.cpp:682 
 #16 0x00002aaaaac31fb4 in Akregator::Folder::slotDeleteExpiredArticles ( 
     this=0xa9eca0) at folder.cpp:294 
 #17 0x00002aaaaac31fb4 in Akregator::Folder::slotDeleteExpiredArticles ( 
     this=0x8c2530) at folder.cpp:294 
 #18 0x00002aaab0e54cdf in Akregator::View::qt_invoke (this=0x6e7ce0, _id=104, 
     _o=0x7fffffc7c360) at akregator_view.moc:441 
 #19 0x00002aaaae5fff88 in QObject::activate_signal (this=0x7e5a00, 
     clist=0x7b0aa0, o=0x7fffffc7c360) at qobject.cpp:2356 
 #20 0x00002aaaae5ffdeb in QObject::activate_signal (this=0x7e5a00, signal=2) 
     at qobject.cpp:2325 
 #21 0x00002aaaae9b3ca4 in QTimer::timeout (this=0x7e5a00) at moc_qtimer.cpp:82 
 #22 0x00002aaaae629f52 in QTimer::event (this=0x7e5a00, e=0x7fffffc7c740) 
     at qtimer.cpp:219 
 #23 0x00002aaaae5937fb in QApplication::internalNotify (this=0x7fffffc7ca80, 
     receiver=0x7e5a00, e=0x7fffffc7c740) at qapplication.cpp:2635 
 #24 0x00002aaaae592b49 in QApplication::notify (this=0x7fffffc7ca80, 
     receiver=0x7e5a00, e=0x7fffffc7c740) at qapplication.cpp:2358 
 #25 0x00002aaaad840d8c in KApplication::notify (this=0x7fffffc7ca80, 
     receiver=0x7e5a00, event=0x7fffffc7c740) at kapplication.cpp:550 
 #26 0x00002aaaabd1e865 in QApplication::sendEvent (receiver=0x2aaab0b30270, 
     event=0xe1a240) at qapplication.h:496 
 #27 0x00002aaaae57fa1b in QEventLoop::activateTimers (this=0x5a1f10) 
     at qeventloop_unix.cpp:556 
 #28 0x00002aaaae53097d in QEventLoop::processEvents (this=0x5a1f10, flags=4) 
     at qeventloop_x11.cpp:389 
 #29 0x00002aaaae5aa868 in QEventLoop::enterLoop (this=0x5a1f10) 
     at qeventloop.cpp:198 
 #30 0x00002aaaae5aa765 in QEventLoop::exec (this=0x5a1f10) 
     at qeventloop.cpp:145 
 #31 0x00002aaaae593948 in QApplication::exec (this=0x7fffffc7ca80) 
     at qapplication.cpp:2758 
 #32 0x000000000040bd42 in main (argc=2, argv=0x62e600) at main.cpp:110 

*** Bug 121247 has been marked as a duplicate of this bug. ***

Created attachment 14691 [details]
Full backtrace

This is a backtrace on an amd64 system with full debug informations (-ggdb),
maybe it can be of help.

Diego: thanks for the detailed backtrace.

Stephan, which architecture do you use? We have three reports now, two of them are on 64bit processors.
I tried to reproduce it here (Pentium M), but to no avail...

*** Bug 122286 has been marked as a duplicate of this bug. ***

Anyone still gets this with 3.5.3 or 3.5.4?

Nobody reported this since February and no further reactions - I close the bug, reopen if you still get it with 3.5.5.