Bug 311125

Summary: Crash while loading a feed
Product: [Applications] konqueror Reporter: Benoit Leffray <benoit.leffray.kde>
Component: khtmlAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: asturm
Priority: NOR    
Version: 4.9.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: akregator kcrash log on trying to open a feed

Description Benoit Leffray 2012-12-04 00:57:36 UTC
Application: akregator (4.9.3)
KDE Platform Version: 4.9.3
Qt Version: 4.8.3
Operating System: Linux 3.5.0-19-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:

I simply clicked on one of my feeds in the left-hand side panel to open it.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee283117c0 (LWP 15027))]

Thread 4 (Thread 0x7fee18a0b700 (LWP 15030)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215
#1  0x00007fee38cf2fa7 in wait (time=30000, this=0x12e3120) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xeaf4e8, time=30000) at thread/qwaitcondition_unix.cpp:158
#3  0x00007fee38ce654f in QThreadPoolThread::run (this=0xe63780) at concurrent/qthreadpool.cpp:141
#4  0x00007fee38cf2aec in QThreadPrivate::start (arg=0xe63780) at thread/qthread_unix.cpp:338
#5  0x00007fee330c6e9a in start_thread (arg=0x7fee18a0b700) at pthread_create.c:308
#6  0x00007fee38217cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fee12a0f700 (LWP 15099)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215
#1  0x00007fee38cf2fa7 in wait (time=30000, this=0x12e3120) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xeaf4e8, time=30000) at thread/qwaitcondition_unix.cpp:158
#3  0x00007fee38ce654f in QThreadPoolThread::run (this=0x31154a0) at concurrent/qthreadpool.cpp:141
#4  0x00007fee38cf2aec in QThreadPrivate::start (arg=0x31154a0) at thread/qthread_unix.cpp:338
#5  0x00007fee330c6e9a in start_thread (arg=0x7fee12a0f700) at pthread_create.c:308
#6  0x00007fee38217cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fee11dff700 (LWP 15104)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:215
#1  0x00007fee38cf2fa7 in wait (time=30000, this=0x12e3120) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xeaf4e8, time=30000) at thread/qwaitcondition_unix.cpp:158
#3  0x00007fee38ce654f in QThreadPoolThread::run (this=0x62c64e0) at concurrent/qthreadpool.cpp:141
#4  0x00007fee38cf2aec in QThreadPrivate::start (arg=0x62c64e0) at thread/qthread_unix.cpp:338
#5  0x00007fee330c6e9a in start_thread (arg=0x7fee11dff700) at pthread_create.c:308
#6  0x00007fee38217cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fee283117c0 (LWP 15027)):
[KCrash Handler]
#6  0x00007fee352ea06b in qobject_cast<KHTMLPart*> (object=<error reading variable: Cannot access memory at address 0x1f0f0000000010>) at /usr/include/qt4/QtCore/qobject.h:380
#7  KHTMLPart::parentPart (this=<optimized out>) at ../../khtml/khtml_part.cpp:5351
#8  0x00007fee352fb755 in isAncestorOrSamePart (p2=<optimized out>, p1=0xc01e90) at ../../khtml/khtml_part.cpp:2258
#9  KHTMLPart::slotLoaderRequestDone (this=0xc01e90, dl=0x27e33b0, obj=<optimized out>) at ../../khtml/khtml_part.cpp:2282
#10 0x00007fee35314bb4 in KHTMLPart::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./khtml_part.moc:307
#11 0x00007fee38e04f5f in QMetaObject::activate (sender=0x951860, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff941c6a80) at kernel/qobject.cpp:3547
#12 0x00007fee354cd57f in khtml::Loader::requestDone (this=this@entry=0x951860, _t1=0x27e33b0, _t2=0x27469d0) at ./loader.moc:188
#13 0x00007fee354d0cbe in khtml::Loader::slotFinished (this=0x951860, job=0x2746910) at ../../khtml/misc/loader.cpp:1263
#14 0x00007fee38e04f5f in QMetaObject::activate (sender=0x2746910, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff941c6c70) at kernel/qobject.cpp:3547
#15 0x00007fee3926cef2 in KJob::result (this=this@entry=0x2746910, _t1=_t1@entry=0x2746910) at ./kjob.moc:208
#16 0x00007fee3926cf30 in KJob::emitResult (this=0x2746910) at ../../kdecore/jobs/kjob.cpp:318
#17 0x00007fee37d70845 in KIO::SimpleJob::slotFinished (this=this@entry=0x2746910) at ../../kio/kio/job.cpp:494
#18 0x00007fee37d77d32 in KIO::TransferJob::slotFinished (this=0x2746910) at ../../kio/kio/job.cpp:1081
#19 0x00007fee38e04f5f in QMetaObject::activate (sender=0x312cb50, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#20 0x00007fee37e13501 in KIO::SlaveInterface::dispatch (this=0x312cb50, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:172
#21 0x00007fee37e105fa in KIO::SlaveInterface::dispatch (this=0x312cb50) at ../../kio/kio/slaveinterface.cpp:88
#22 0x00007fee37e04a5e in KIO::Slave::gotInput (this=0x312cb50) at ../../kio/kio/slave.cpp:344
#23 0x00007fee38e04f5f in QMetaObject::activate (sender=0x3116e60, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#24 0x00007fee37d45732 in dequeue (this=<optimized out>) at ../../kio/kio/connection.cpp:82
#25 KIO::ConnectionPrivate::dequeue (this=0x27c84b0) at ../../kio/kio/connection.cpp:71
#26 0x00007fee38e0443e in QObject::event (this=0x3116e60, e=<optimized out>) at kernel/qobject.cpp:1195
#27 0x00007fee397d1e9c in QApplicationPrivate::notify_helper (this=this@entry=0x8f7360, receiver=receiver@entry=0x3116e60, e=e@entry=0xe4d220) at kernel/qapplication.cpp:4562
#28 0x00007fee397d630a in QApplication::notify (this=0x7fff941c7ea0, receiver=0x3116e60, e=0xe4d220) at kernel/qapplication.cpp:4423
#29 0x00007fee3a4da1d6 in KApplication::notify (this=0x7fff941c7ea0, receiver=0x3116e60, event=0xe4d220) at ../../kdeui/kernel/kapplication.cpp:311
#30 0x00007fee38def56e in QCoreApplication::notifyInternal (this=0x7fff941c7ea0, receiver=receiver@entry=0x3116e60, event=event@entry=0xe4d220) at kernel/qcoreapplication.cpp:915
#31 0x00007fee38df33f1 in sendEvent (event=0xe4d220, receiver=0x3116e60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8be380) at kernel/qcoreapplication.cpp:1539
#33 0x00007fee38e1da63 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#34 postEventSourceDispatch (s=0x8ff970) at kernel/qeventdispatcher_glib.cpp:279
#35 0x00007fee32bf7ab5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007fee32bf7de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007fee32bf7ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007fee38e1dbf6 in QEventDispatcherGlib::processEvents (this=0x8f7b40, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#39 0x00007fee39876c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#40 0x00007fee38dee2bf in QEventLoop::processEvents (this=this@entry=0x7fff941c7cc0, flags=...) at kernel/qeventloop.cpp:149
#41 0x00007fee38dee548 in QEventLoop::exec (this=0x7fff941c7cc0, flags=...) at kernel/qeventloop.cpp:204
#42 0x00007fee38df3708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#43 0x0000000000407c63 in main (argc=<optimized out>, argv=<optimized out>) at ../../../akregator/src/main.cpp:103

Reported using DrKonqi
Comment 1 Andreas Sturmlechner 2013-02-02 14:02:56 UTC
This also happens to me in 4.10 RC3 (while RC2 was fine).

I tried with a completely new user and fresh homedir, started akregator standalone - and it crashed as soon as clicking onto a feed.
Comment 2 Andreas Sturmlechner 2013-02-02 15:36:43 UTC
Created attachment 76871 [details]
akregator kcrash log on trying to open a feed

Other than that, I get akregator also randomly crashing when:
- right after the window appearing without clicking anything
- the restore session dialog appears after one of the above crashes - instant crash without click even there

So right now, for me, akregator is a total wreck.
Comment 3 Andreas Sturmlechner 2013-02-03 10:32:34 UTC
My apologies. Trouble was caused by using -fgraphite-identity on kdelibs...
Comment 4 Andrew Crouthamel 2018-10-29 22:32:29 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-13 14:40:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2018-11-29 09:42:47 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!