Version: 3.5.2 (using KDE Devel) Installed from: Compiled sources Compiler: gcc-4.1.0 OS: Linux A few hours after kde-3.5.2 installation, akregator has crashed on me, for a different reason than the rest of my open bugs. x86_64, qt-3.6.6, kde-3.5.2, gcc-4.1.0 Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47747346333024 (LWP 6630)] [KCrash handler] #5 0x00002b6d0b7dc22a in raise () from /lib/libc.so.6 #6 0x00002b6d0b7dd540 in abort () from /lib/libc.so.6 #7 0x00002b6d0b7d5756 in __assert_fail () from /lib/libc.so.6 #8 0x00002b6d06954e3a in KHTMLPart::slotInfoMessage (this=0x782ca0, kio_job=<value optimized out>, msg=@0xf1d370) at khtml_part.cpp:1516 #9 0x00002b6d06966fc7 in KHTMLPart::qt_invoke (this=0x782ca0, _id=<value optimized out>, _o=0x7fffa53e9640) at khtml_part.moc:502 #10 0x00002b6d0bbb4852 in Akregator::Viewer::qt_invoke (this=0x782ca0, _id=17, _o=0x7fffa53e9640) at viewer.moc:201 #11 0x00002b6d0bbb85d5 in Akregator::ArticleViewer::qt_invoke (this=0x782ca0, _id=17, _o=0x7fffa53e9640) at articleviewer.moc:136 #12 0x00002b6d0922560c in QObject::activate_signal (this=0x1599bf0, clist=0x150c2e0, o=0x7fffa53e9640) at kernel/qobject.cpp:2356 #13 0x00002b6d077d5c22 in KIO::Job::infoMessage (this=0x1599bf0, t0=0x1599bf0, t1=@0xce7c00) at jobclasses.moc:189 #14 0x00002b6d077da0fd in KIO::SimpleJob::qt_invoke (this=0x1599bf0, _id=9, _o=0x7fffa53e9850) at jobclasses.moc:419 #15 0x00002b6d077da1ad in KIO::TransferJob::qt_invoke (this=0x1599bf0, _id=9, _o=0x7fffa53e9850) at jobclasses.moc:1082 #16 0x00002b6d0922560c in QObject::activate_signal (this=0x17f30a0, clist=0x12518e0, o=0x7fffa53e9850) at kernel/qobject.cpp:2356 #17 0x00002b6d09225cec in QObject::activate_signal (this=0x17f30a0, signal=21, param=@0x7fffa53e98a0) at kernel/qobject.cpp:2451 #18 0x00002b6d077c64e4 in KIO::SlaveInterface::infoMessage (this=0x17f30a0, t0=<value optimized out>) at slaveinterface.moc:382 #19 0x00002b6d077c8189 in KIO::SlaveInterface::dispatch (this=0x17f30a0, _cmd=26, rawdata=@0x7fffa53e9be0) at slaveinterface.cpp:369 #20 0x00002b6d077c8a40 in KIO::SlaveInterface::dispatch (this=0x17f30a0) at slaveinterface.cpp:173 #21 0x00002b6d077c42cd in KIO::Slave::gotInput (this=0x17f30a0) at slave.cpp:300 #22 0x00002b6d077c5e7d in KIO::Slave::qt_invoke (this=0x17f30a0, _id=4, _o=0x7fffa53e9dd0) at slave.moc:113 #23 0x00002b6d0922560c in QObject::activate_signal (this=0x1614c60, clist=0x880780, o=0x7fffa53e9dd0) at kernel/qobject.cpp:2356 #24 0x00002b6d092262ca in QObject::activate_signal (this=0x1614c60, signal=2, param=88) at kernel/qobject.cpp:2449 #25 0x00002b6d09617886 in QSocketNotifier::activated (this=0x1614c60, t0=88) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #26 0x00002b6d09249ab0 in QSocketNotifier::event (this=0x1614c60, e=0x7fffa53ea2b0) at kernel/qsocketnotifier.cpp:258 #27 0x00002b6d091b068e in QApplication::internalNotify (this=0x7fffa53ea660, receiver=0x1614c60, e=0x7fffa53ea2b0) at kernel/qapplication.cpp:2635 #28 0x00002b6d091b0931 in QApplication::notify (this=0x7fffa53ea660, receiver=0x1614c60, e=0x7fffa53ea2b0) at kernel/qapplication.cpp:2358 #29 0x00002b6d0845f9ea in KApplication::notify (this=0x7fffa53ea660, receiver=0x1614c60, event=0x7fffa53ea2b0) at kapplication.cpp:550 #30 0x00002b6d06945ca0 in QApplication::sendEvent ( receiver=0xffffffffffffffff, event=0x6) at qapplication.h:496 #31 0x00002b6d091a0a80 in QEventLoop::activateSocketNotifiers (this=0x6205e0) at kernel/qeventloop_unix.cpp:578 #32 0x00002b6d0914c592 in QEventLoop::processEvents (this=0x6205e0, flags=4) at kernel/qeventloop_x11.cpp:383 #33 0x00002b6d091cc626 in QEventLoop::enterLoop (this=0x6205e0) at kernel/qeventloop.cpp:198 #34 0x00002b6d091cc52f in QEventLoop::exec (this=0x6205e0) at kernel/qeventloop.cpp:145 #35 0x00002b6d091af23a in QApplication::exec (this=0x7fffa53ea660) at kernel/qapplication.cpp:2758 #36 0x000000000040bd49 in main (argc=<value optimized out>, argv=0x6ac210) at main.cpp:110
Is the crash reproducible?
| Is the crash reproducible? Hrm, no. I guess I should have mentioned it happened out of nowhere, I wasn't even in the workspace.
Hmm, this crash happens in article viewer, so it's more interesting to Akregator than the occasional crash in a browser tab due to KHTML bugs. For how long did you leave akregator unattended? Minutes, hours? Do you use Combined View (all articles in the main html view), or the "Load the full website when reading articles" feed option? It looks like something went wrong with a KIO job associated with the part and it tried to show an error popup. Which should only happen if there was some activity...
In reply to comment #3 | Hmm, this crash happens in article viewer, so it's more interesting to | Akregator than the occasional crash in a browser tab due to KHTML bugs. Superb. | For how long did you leave akregator unattended? Minutes, hours? I couldn't say definitively, but it was probably less than an hour. | Do you use Combined View (all articles in the main html view), or the "Load | the full website when reading articles" feed option? I use 'Normal View', I use the 'Load the full website' on some websites, specifically if the information received is not useful (like some websites only display the title in the body, for sites like those I load full website') | It looks like something went wrong with a KIO job associated with the part | and it tried to show an error popup. Which should only happen if there was | some activity... Hrm, you have me second guessing myself right now. I guess next time it happens I will write a much more detailed bug report, reporting exactly what was happening, should have done it this time.
I think this is a dupe of 126812. Reopen if you get this crash in >= 3.5.3. *** This bug has been marked as a duplicate of 126812 ***