Bug 137372 - crash on page display (100% repro, with backtrace)
Summary: crash on page display (100% repro, with backtrace)
Status: RESOLVED DUPLICATE of bug 126812
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-15 02:01 UTC by Marcin Gryszkalis
Modified: 2006-11-15 15:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Gryszkalis 2006-11-15 02:01:32 UTC
Version:           1.2.5 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1 
OS:                Linux

akregator crashes when trying to display one article (I have "load full website" option on).

The article is at http://googleblog.blogspot.com - it is
"Desktop refreshed" from 11/13/2006 01:01:00 PM (note that there are 2 articles with such title, the other one doesn't cause crash). The link under summary is
http://googleblog.blogspot.com/2006/11/desktop-refreshed.html#links
and it gives "404 not found" error (maybe this is the cause?)

The feed is at
http://googleblog.blogspot.com/atom.xml

Here's the backtrace:


[KCrash handler]
#9  0xb7825a54 in QGuardedPtr<khtml::RenderPart>::operator khtml::RenderPart*
    (this=0x28) at /usr/qt/3/include/qguardedptr.h:117
#10 0xb781691c in KHTMLPart::slotFinished (this=0x816cb20, job=0x86ba838)
    at khtml_part.cpp:1846
#11 0xb781de26 in KHTMLPart::qt_invoke (this=0x816cb20, _id=19, _o=0xbfff8a84)
    at khtml_part.moc:503
#12 0xb581d500 in Akregator::Viewer::qt_invoke (this=0x816cb20, _id=19, 
    _o=0xbfff8a84) at viewer.moc:201
#13 0xb5821968 in Akregator::ArticleViewer::qt_invoke (this=0x816cb20, 
    _id=19, _o=0xbfff8a84) at articleviewer.moc:136
#14 0xb62dafb4 in QObject::activate_signal (this=0x86ba838, clist=0x8595728, 
    o=0xbfff8a84) at kernel/qobject.cpp:2380
#15 0xb71badf1 in KIO::Job::result (this=0x86ba838, t0=0x86ba838)
    at jobclasses.moc:162
#16 0xb71c09ee in KIO::Job::emitResult (this=0x86ba838) at job.cpp:226
#17 0xb71c0dff in KIO::SimpleJob::slotFinished (this=0x86ba838) at job.cpp:574
#18 0xb71c139f in KIO::TransferJob::slotFinished (this=0x86ba838)
    at job.cpp:944
#19 0xb71bf65b in KIO::TransferJob::qt_invoke (this=0x86ba838, _id=17, 
    _o=0xbfff8d8c) at jobclasses.moc:1071
#20 0xb62dae87 in QObject::activate_signal (this=0x85d71d0, clist=0x80d6a88, 
    o=0xbfff8d8c) at kernel/qobject.cpp:2356
#21 0xb62dbc20 in QObject::activate_signal (this=0x85d71d0, signal=6)
    at kernel/qobject.cpp:2325
#22 0xb71ab4c3 in KIO::SlaveInterface::finished (this=0x85d71d0)
    at slaveinterface.moc:226
#23 0xb71acc6b in KIO::SlaveInterface::dispatch (this=0x85d71d0, _cmd=104, 
    rawdata=@0xbfff8f64) at slaveinterface.cpp:243
#24 0xb71ad386 in KIO::SlaveInterface::dispatch (this=0x85d71d0)
    at slaveinterface.cpp:173
#25 0xb71a8857 in KIO::Slave::gotInput (this=0x85d71d0) at slave.cpp:300
#26 0xb71aa50b in KIO::Slave::qt_invoke (this=0x85d71d0, _id=4, _o=0xbfff90a8)
    at slave.moc:113
#27 0xb62dae87 in QObject::activate_signal (this=0x85912d8, clist=0x85f2fe8, 
    o=0xbfff90a8) at kernel/qobject.cpp:2356
#28 0xb62dba06 in QObject::activate_signal (this=0x85912d8, signal=2, 
    param=45) at kernel/qobject.cpp:2449
#29 0xb66d8d5f in QSocketNotifier::activated (this=0x85912d8, t0=45)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#30 0xb6302326 in QSocketNotifier::event (this=0x85912d8, e=0xbfff93dc)
    at kernel/qsocketnotifier.cpp:258
#31 0xb62665b7 in QApplication::internalNotify (this=0xbfff9650, 
    receiver=0x85912d8, e=0xbfff93dc) at kernel/qapplication.cpp:2635
#32 0xb626852f in QApplication::notify (this=0xbfff9650, receiver=0x85912d8, 
    e=0xbfff93dc) at kernel/qapplication.cpp:2358
#33 0xb6b4ec96 in KApplication::notify (this=0xbfff9650, receiver=0x85912d8, 
    event=0xbfff93dc) at kapplication.cpp:550
#34 0xb77fb65f in QApplication::sendEvent (receiver=0x85912d8, 
    event=0xbfff93dc) at /usr/qt/3/include/qapplication.h:496
#35 0xb6256d46 in QEventLoop::activateSocketNotifiers (this=0x8087aa8)
    at kernel/qeventloop_unix.cpp:578
#36 0xb6206d34 in QEventLoop::processEvents (this=0x8087aa8, flags=4)
    at kernel/qeventloop_x11.cpp:383
#37 0xb62845d1 in QEventLoop::enterLoop (this=0x8087aa8)
    at kernel/qeventloop.cpp:198
#38 0xb62843f2 in QEventLoop::exec (this=0x8087aa8)
    at kernel/qeventloop.cpp:145
#39 0xb626827b in QApplication::exec (this=0xbfff9650)
    at kernel/qapplication.cpp:2758
#40 0x08051678 in main (argc=0, argv=0xbfff9814) at main.cpp:110
Comment 1 Marcin Gryszkalis 2006-11-15 02:03:43 UTC
Note: after switching "load full website" off I can display summary without problem and I can click "complete story" link (to get mentioned 404 but no crash).
Comment 2 Tommi Tervo 2006-11-15 15:08:38 UTC

*** This bug has been marked as a duplicate of 126812 ***