Bugzilla – Bug 154811
akregator crashes on startup due to corrupt feed cache
Last modified: 2008-12-10 23:16:21 UTC
akregator crashes on startup with the following crash information: System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1235020112 (LWP 16827)] [KCrash handler] #6 c4_FormatB::InitOffsets (this=0x837e588, sizes_=@0x837e5b4) at univ.inl:101 #7 0xb5999436 in c4_FormatB::Define (this=0x837e588, ptr_=0xbf997d80) at format.cpp:439 #8 0xb598e499 in c4_HandlerSeq::Prepare (this=0x837e100, ptr_=0xbf997d80, selfDesc_=true) at handler.cpp:348 #9 0xb5997275 in c4_Persist::LoadAll (this=0x837e0b0) at persist.cpp:1043 #10 0xb59974dd in c4_Storage (this=0x82d7b60, fname_=0x837dee8 "/home/robert/.kde/share/apps/akregator/Archive/http___www.planetsuse.org_rss10.xml.mk4", mode_=1) at store.cpp:217 #11 0xb597a666 in FeedStorageMK4Impl (this=0x837ede0, url=@0x837d760, main=0x815b970) at feedstoragemk4impl.cpp:150 #12 0xb597acb1 in Akregator::Backend::StorageMK4Impl::archiveFor ( this=0x815b970, url=@0x837d760) at storagemk4impl.cpp:254 #13 0xb7f7f51f in Akregator::Feed::loadArticles (this=0x837c200) at feed.cpp:212 #14 0xb7f808f0 in Akregator::Feed::fromOPML (e=@0xbf998110) at feed.cpp:164 #15 0xb7f80ca5 in Akregator::FeedList::parseChildNodes (this=0x826e7e8, node=@0xbf998180, parent=0x8357480) at feedlist.cpp:117 #16 0xb7f80dac in Akregator::FeedList::parseChildNodes (this=0x826e7e8, node=@0xbf99820c, parent=0x826e6e8) at feedlist.cpp:135 #17 0xb7f811ce in Akregator::FeedList::readFromXML (this=0x826e7e8, doc=@0xbf998384) at feedlist.cpp:175 #18 0xb61603bc in Akregator::View::loadFeeds (this=0x815dd30, doc=@0xbf998384, parent=0x0) at akregator_view.cpp:541 #19 0xb61949db in Akregator::Part::openFile (this=0x814cd50) at akregator_part.cpp:410 #20 0xb6183dec in Akregator::Part::openURL (this=0x814cd50, url=@0xbf998464) at akregator_part.cpp:299 #21 0xb615842b in Akregator::Part::openStandardFeedList (this=0x814cd50) at akregator_part.cpp:304 #22 0xb6168650 in Akregator::AkregatorPartIface::process (this=0x814cdfc, fun=@0xbf998734, data=@0xbf9987a4, replyType=@0xbf9986d4, replyData=@0xbf9986cc) at akregator_partiface_skel.cpp:39 #23 0xb7851f37 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4 #24 0xb7856402 in DCOPClient::send () from /opt/kde3/lib/libDCOP.so.4 #25 0xb7856a3f in DCOPRef::sendInternal () from /opt/kde3/lib/libDCOP.so.4 #26 0x08051bb5 in Akregator::Application::newInstance (this=0xbf998e00) at dcopref.h:1118 #27 0xb79bfd4d in KUniqueApplication::processDelayed () from /opt/kde3/lib/libkdecore.so.4 #28 0xb79f58d8 in KUniqueApplication::qt_invoke () from /opt/kde3/lib/libkdecore.so.4 #29 0xb73c5fed in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #30 0xb76fcc7e in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb73e1ba7 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb73e8f93 in QSingleShotTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb7366d57 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb7367a01 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb7a21383 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #36 0xb735bdc5 in QEventLoop::activateTimers () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb73169e0 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #38 0xb737da68 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb737d8fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0xb73667ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #41 0x0805133e in main (argc=) at main.cpp:110 #42 0xb6f6783c in __libc_start_main () from /lib/libc.so.6 #43 0x08050081 in _start ()
default configuration? can you attach $KDEHOME/share/config/akregatorrc and $KDEHOME/share/apps/akregator ?
Created attachment 71140 [details] the requested data
it's eating memory like mad
your www.kde.org/kde-look-content.rdf is broken and akregator's backend does not cope with invalid data ;( But I'll add the patch from http://bugs.kde.org/show_bug.cgi?id=116482 to our packages to make it less likely. Can you please see there if you're part of the target group?
the binary file format has exactly no way to figure if it's corrupt or not ;(
What exactly do you mean by "you're part of the target group"? The description in the KDE bug report sounds similar but for me a crash window does appear but no memory corruption message from glibc.
Robert: the bug report talks about several scenarios where a corrupted file is likely and I'd like to know if you did something unusual to your files.
I did just use the tool in a normal way. I did not change anything at the files manually. But actually my system crashed sometimes completely due to the ATI driver while the tool was open in the background.
*** Bug 198107 has been marked as a duplicate of this bug. ***
*** Bug 349040 has been marked as a duplicate of this bug. ***
*** Bug 371701 has been marked as a duplicate of this bug. ***
Apparently upstream says the bug is unfixable. I will keep tabs on the upstream bugreport, but I fear a real fix will only come when akregator is ported to Akonadi.