Application: konqueror (4.10.1) KDE Platform Version: 4.10.1 Qt Version: 4.8.4 Operating System: Linux 3.8.4-202.fc18.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: (Memory is fading due to intervening interruptions (like creating a KDE account without trusting a browser on this machine)). I had a small number of tabs open in one window. I pressed the middle mouse button on a link. Boom. The system is a new Fedora 18 x86-64 installation. -- Backtrace: Application: Konqueror (kdeinit4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fc5bd9c9880 (LWP 13529))] Thread 9 (Thread 0x7fc5a9df6700 (LWP 13533)): #0 0x000000377620aacf in __pthread_mutex_unlock_usercnt (mutex=0x7fc5a4000a60, decr=decr@entry=1) at pthread_mutex_unlock.c:52 #1 0x000000377620ab2a in __GI___pthread_mutex_unlock (mutex=<optimized out>) at pthread_mutex_unlock.c:297 #2 0x0000003778684dd1 in g_mutex_unlock (mutex=mutex@entry=0x7fc5a40009a0) at gthread-posix.c:229 #3 0x0000003778647612 in g_main_context_prepare (context=context@entry=0x7fc5a40009a0, priority=priority@entry=0x7fc5a9df5b78) at gmain.c:3020 #4 0x0000003778647c4b in g_main_context_iterate (context=context@entry=0x7fc5a40009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3270 #5 0x0000003778647e44 in g_main_context_iteration (context=0x7fc5a40009a0, may_block=1) at gmain.c:3351 #6 0x00007fc5bfe60126 in QEventDispatcherGlib::processEvents (this=0x7fc5a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x00007fc5bfe3080f in QEventLoop::processEvents (this=this@entry=0x7fc5a9df5cd0, flags=...) at kernel/qeventloop.cpp:149 #8 0x00007fc5bfe30a98 in QEventLoop::exec (this=0x7fc5a9df5cd0, flags=...) at kernel/qeventloop.cpp:204 #9 0x00007fc5bfd32980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #10 0x00007fc5bfe1103f in QInotifyFileSystemWatcherEngine::run (this=0x2d40960) at io/qfilesystemwatcher_inotify.cpp:256 #11 0x00007fc5bfd3595c in QThreadPrivate::start (arg=0x2d40960) at thread/qthread_unix.cpp:338 #12 0x0000003776207d15 in start_thread (arg=0x7fc5a9df6700) at pthread_create.c:308 #13 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 8 (Thread 0x7fc5a19b3700 (LWP 13564)): #0 0x0000003775ee998d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0000003778647d24 in g_main_context_poll (priority=2147483647, n_fds=3, fds=0x7fc5900010c0, timeout=-1, context=0x3a1c9e0) at gmain.c:3584 #2 g_main_context_iterate (context=0x3a1c9e0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285 #3 0x0000003778648182 in g_main_loop_run (loop=0x349c4c0) at gmain.c:3484 #4 0x0000003779acc546 in gdbus_shared_thread_func (user_data=0x3a1c9b0) at gdbusprivate.c:277 #5 0x000000377866b605 in g_thread_proxy (data=0x3a4ced0) at gthread.c:797 #6 0x0000003776207d15 in start_thread (arg=0x7fc5a19b3700) at pthread_create.c:308 #7 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 7 (Thread 0x7fc5a3fff700 (LWP 24752)): #0 0x000000377620e12d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x00000037786840df in read (__nbytes=16, __buf=0x7fc5a3ffeae0, __fd=<optimized out>) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x3a1c760) at gwakeup.c:212 #3 0x00000037786478b4 in g_main_context_check (context=context@entry=0x7fc59c007470, max_priority=2147483647, fds=fds@entry=0x7fc59c006430, n_fds=n_fds@entry=1) at gmain.c:3129 #4 0x0000003778647cc2 in g_main_context_iterate (context=context@entry=0x7fc59c007470, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3287 #5 0x0000003778647e44 in g_main_context_iteration (context=0x7fc59c007470, may_block=1) at gmain.c:3351 #6 0x00007fc5bfe60126 in QEventDispatcherGlib::processEvents (this=0x7fc59c0060c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x00007fc5bfe3080f in QEventLoop::processEvents (this=this@entry=0x7fc5a3ffecd0, flags=...) at kernel/qeventloop.cpp:149 #8 0x00007fc5bfe30a98 in QEventLoop::exec (this=0x7fc5a3ffecd0, flags=...) at kernel/qeventloop.cpp:204 #9 0x00007fc5bfd32980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #10 0x00007fc5b5cc2cde in KIO::NameLookUpThread::run (this=0x3c088b0) at /usr/src/debug/kdelibs-4.10.1/kio/kio/hostinfo.cpp:226 #11 0x00007fc5bfd3595c in QThreadPrivate::start (arg=0x3c088b0) at thread/qthread_unix.cpp:338 #12 0x0000003776207d15 in start_thread (arg=0x7fc5a3fff700) at pthread_create.c:308 #13 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 6 (Thread 0x7fc58ffff700 (LWP 24756)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00007fc5975279bd in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7fc597f12d00 <WTF::pageheap_memory>) at wtf/FastMalloc.cpp:2495 #2 0x00007fc597527ac9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at wtf/FastMalloc.cpp:1618 #3 0x0000003776207d15 in start_thread (arg=0x7fc58ffff700) at pthread_create.c:308 #4 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 5 (Thread 0x7fc58f7fe700 (LWP 24757)): #0 0x0000003775ee998d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0000003778647d24 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fc5840025c0, timeout=9403, context=0x7fc5840009a0) at gmain.c:3584 #2 g_main_context_iterate (context=context@entry=0x7fc5840009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285 #3 0x0000003778647e44 in g_main_context_iteration (context=0x7fc5840009a0, may_block=1) at gmain.c:3351 #4 0x00007fc5bfe60126 in QEventDispatcherGlib::processEvents (this=0x7fc5840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x00007fc5bfe3080f in QEventLoop::processEvents (this=this@entry=0x7fc58f7fdd00, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007fc5bfe30a98 in QEventLoop::exec (this=0x7fc58f7fdd00, flags=...) at kernel/qeventloop.cpp:204 #7 0x00007fc5bfd32980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #8 0x00007fc5bfd3595c in QThreadPrivate::start (arg=0x38490b0) at thread/qthread_unix.cpp:338 #9 0x0000003776207d15 in start_thread (arg=0x7fc58f7fe700) at pthread_create.c:308 #10 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 4 (Thread 0x7fc58c90b700 (LWP 24786)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00007fc58c92d163 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x0000003776207d15 in start_thread (arg=0x7fc58c90b700) at pthread_create.c:308 #3 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 3 (Thread 0x7fc543fff700 (LWP 24787)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00007fc58c92d163 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x0000003776207d15 in start_thread (arg=0x7fc543fff700) at pthread_create.c:308 #3 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 2 (Thread 0x7fc5437fe700 (LWP 24788)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00007fc58c92d163 in queue_processor(void*) () from /usr/lib64/IcedTeaPlugin.so #2 0x0000003776207d15 in start_thread (arg=0x7fc5437fe700) at pthread_create.c:308 #3 0x0000003775ef246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 1 (Thread 0x7fc5bd9c9880 (LWP 13529)): [KCrash Handler] #6 operator QtSharedPointer::ExternalRefCountData* (this=0x80) at ../../src/corelib/thread/qbasicatomic.h:169 #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=0x41bbb00) at tools/qsharedpointer.cpp:1255 #8 0x00007fc5be2cc9f2 in QWeakPointer<QObject> (ptr=0x41bbb00, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0x41bbb00, this=0x40322c0) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7fff304b9210, object=0x41bbb00) at access/qnetworkrequest.cpp:565 #11 0x00007fc59721bbd1 in WebCore::ResourceRequest::toNetworkRequest (this=0x7fff304b9270, originatingFrame=0x41bbb00) at platform/network/qt/ResourceRequestQt.cpp:50 #12 0x00007fc59722062c in WebCore::QNetworkReplyHandler::redirect (this=this@entry=0x53fbaf0, response=..., redirection=...) at platform/network/qt/QNetworkReplyHandler.cpp:569 #13 0x00007fc597221320 in WebCore::QNetworkReplyHandler::sendResponseIfNeeded (this=0x53fbaf0) at platform/network/qt/QNetworkReplyHandler.cpp:520 #14 0x00007fc59721ece2 in flush (this=0x53fbb28) at platform/network/qt/QNetworkReplyHandler.cpp:195 #15 WebCore::QNetworkReplyHandlerCallQueue::flush (this=0x53fbb28) at platform/network/qt/QNetworkReplyHandler.cpp:187 #16 0x00007fc59721fcfa in ~QueueLocker (this=<synthetic pointer>, __in_chrg=<optimized out>) at platform/network/qt/QNetworkReplyHandler.cpp:203 #17 WebCore::QNetworkReplyWrapper::receiveMetaData (this=0x53faeb0) at platform/network/qt/QNetworkReplyHandler.cpp:276 #18 0x00007fc5bfe46eef in QMetaObject::activate (sender=0x52ad550, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #19 0x00007fc5bfe39907 in QMetaMethod::invoke (this=this@entry=0x7fff304b9b10, object=object@entry=0x52ad550, connectionType=Qt::DirectConnection, connectionType@entry=Qt::AutoConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1664 #20 0x00007fc5bfe3bcdc in QMetaObject::invokeMethod (obj=0x52ad550, member=<optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1179 #21 0x00007fc5b5be21cc in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::AutoConnection, member=0x7fc5b5d452fa "finished", obj=0x52ad550) at /usr/include/QtCore/qobjectdefs.h:418 #22 KDEPrivate::AccessManagerReply::emitFinished (this=this@entry=0x52ad550, state=state@entry=true, type=type@entry=Qt::AutoConnection) at /usr/src/debug/kdelibs-4.10.1/kio/kio/accessmanagerreply_p.cpp:484 #23 0x00007fc5b5be34c5 in KDEPrivate::AccessManagerReply::slotResult (this=0x52ad550, kJob=0x547e0b0) at /usr/src/debug/kdelibs-4.10.1/kio/kio/accessmanagerreply_p.cpp:427 #24 0x00007fc5bfe46eef in QMetaObject::activate (sender=0x547e0b0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff304ba0c0) at kernel/qobject.cpp:3539 #25 0x00007fc5c053f1b2 in KJob::result (this=this@entry=0x547e0b0, _t1=_t1@entry=0x547e0b0) at /usr/src/debug/kdelibs-4.10.1/x86_64-redhat-linux-gnu/kdecore/kjob.moc:207 #26 0x00007fc5c053f1f0 in KJob::emitResult (this=0x547e0b0) at /usr/src/debug/kdelibs-4.10.1/kdecore/jobs/kjob.cpp:318 #27 0x00007fc5b5c16305 in KIO::SimpleJob::slotFinished (this=this@entry=0x547e0b0) at /usr/src/debug/kdelibs-4.10.1/kio/kio/job.cpp:494 #28 0x00007fc5b5c1d812 in KIO::TransferJob::slotFinished (this=0x547e0b0) at /usr/src/debug/kdelibs-4.10.1/kio/kio/job.cpp:1081 #29 0x00007fc5bfe46eef in QMetaObject::activate (sender=0x41c8490, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #30 0x00007fc5b5cb9121 in KIO::SlaveInterface::dispatch (this=0x41c8490, _cmd=104, rawdata=...) at /usr/src/debug/kdelibs-4.10.1/kio/kio/slaveinterface.cpp:172 #31 0x00007fc5b5cb61fa in KIO::SlaveInterface::dispatch (this=0x41c8490) at /usr/src/debug/kdelibs-4.10.1/kio/kio/slaveinterface.cpp:88 #32 0x00007fc5b5caa75e in KIO::Slave::gotInput (this=0x41c8490) at /usr/src/debug/kdelibs-4.10.1/kio/kio/slave.cpp:344 #33 0x00007fc5bfe46eef in QMetaObject::activate (sender=0x41cd7e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #34 0x00007fc5b5beb252 in dequeue (this=<optimized out>) at /usr/src/debug/kdelibs-4.10.1/kio/kio/connection.cpp:82 #35 KIO::ConnectionPrivate::dequeue (this=0x41c0a10) at /usr/src/debug/kdelibs-4.10.1/kio/kio/connection.cpp:71 #36 0x00007fc5bfe463ce in QObject::event (this=0x41cd7e0, e=<optimized out>) at kernel/qobject.cpp:1194 #37 0x00007fc5bf1e15cc in QApplicationPrivate::notify_helper (this=this@entry=0x25f60f0, receiver=receiver@entry=0x41cd7e0, e=e@entry=0x4f75990) at kernel/qapplication.cpp:4562 #38 0x00007fc5bf1e5a4a in QApplication::notify (this=0x7fff304bb410, receiver=0x41cd7e0, e=0x4f75990) at kernel/qapplication.cpp:4423 #39 0x00007fc5c0b253c6 in KApplication::notify (this=0x7fff304bb410, receiver=0x41cd7e0, event=0x4f75990) at /usr/src/debug/kdelibs-4.10.1/kdeui/kernel/kapplication.cpp:311 #40 0x00007fc5bfe31abe in QCoreApplication::notifyInternal (this=0x7fff304bb410, receiver=receiver@entry=0x41cd7e0, event=event@entry=0x4f75990) at kernel/qcoreapplication.cpp:946 #41 0x00007fc5bfe35571 in sendEvent (event=0x4f75990, receiver=0x41cd7e0) at kernel/qcoreapplication.h:231 #42 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x25732d0) at kernel/qcoreapplication.cpp:1570 #43 0x00007fc5bfe5ff73 in sendPostedEvents () at kernel/qcoreapplication.h:236 #44 postEventSourceDispatch (s=s@entry=0x25f6880) at kernel/qeventdispatcher_glib.cpp:279 #45 0x0000003778647a55 in g_main_dispatch (context=0x25fb200) at gmain.c:2715 #46 g_main_context_dispatch (context=context@entry=0x25fb200) at gmain.c:3219 #47 0x0000003778647d88 in g_main_context_iterate (context=context@entry=0x25fb200, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290 #48 0x0000003778647e44 in g_main_context_iteration (context=0x25fb200, may_block=1) at gmain.c:3351 #49 0x00007fc5bfe60106 in QEventDispatcherGlib::processEvents (this=0x25f7340, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #50 0x00007fc5bf28173e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #51 0x00007fc5bfe3080f in QEventLoop::processEvents (this=this@entry=0x7fff304bb110, flags=...) at kernel/qeventloop.cpp:149 #52 0x00007fc5bfe30a98 in QEventLoop::exec (this=0x7fff304bb110, flags=...) at kernel/qeventloop.cpp:204 #53 0x00007fc5bfe35888 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #54 0x00007fc5b6e2ee02 in kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kde-baseapps-4.10.1/konqueror/src/konqmain.cpp:227 #55 0x000000000040822a in launch (argc=argc@entry=2, _name=_name@entry=0x25cca38 "/usr/bin/konqueror", args=0x25cca54 "", args@entry=0x25cca4b "--silent", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x25cca5c "", reset_env=false, tty=tty@entry=0x0, avoid_loops=false, startup_id_str=startup_id_str@entry=0x40aaae "0") at /usr/src/debug/kdelibs-4.10.1/kinit/kinit.cpp:726 #56 0x00000000004090bb in handle_launcher_request (sock=7, who=<optimized out>) at /usr/src/debug/kdelibs-4.10.1/kinit/kinit.cpp:1218 #57 0x0000000000409700 in handle_requests (waitForPid=waitForPid@entry=0) at /usr/src/debug/kdelibs-4.10.1/kinit/kinit.cpp:1411 #58 0x0000000000405307 in main (argc=2, argv=<optimized out>, envp=0x7fff304bc340) at /usr/src/debug/kdelibs-4.10.1/kinit/kinit.cpp:1899 This bug may be a duplicate of or related to bug 316328. Possible duplicates by query: bug 316328. Reported using DrKonqi
*** Bug 316328 has been marked as a duplicate of this bug. ***
*** Bug 317753 has been marked as a duplicate of this bug. ***
The crash is upstream in the QtWebKit library which is used by kwebkitpart. Can any of you reliably reproduce the crash ? I have not seen any such crash on my own system (ArchLinux) with either qtwebkit-2.2.x nor the current version I am using QtWebKit v2.3.
*** Bug 319441 has been marked as a duplicate of this bug. ***
Created attachment 79877 [details] New crash information added by DrKonqi konqueror (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4 - What I was doing when the application crashed: I was browsing price comparison site heureka.cz Konqueror crashed right after I've chosen to sort by price from the drop down option list. -- Backtrace (Reduced): #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=0x2b06310) at tools/qsharedpointer.cpp:1257 #8 0x00000037288799f2 in QWeakPointer<QObject> (ptr=0x2b06310, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0x2b06310, this=0x435ed30) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7fff003b6400, object=0x2b06310) at access/qnetworkrequest.cpp:565 #11 0x000000372e90abd1 in WebCore::ResourceRequest::toNetworkRequest (this=0x7fff003b6460, originatingFrame=0x2b06310) at platform/network/qt/ResourceRequestQt.cpp:50
Created attachment 80111 [details] New crash information added by DrKonqi konqueror (4.10.2) on KDE Platform 4.10.3 using Qt 4.8.4 - What I was doing when the application crashed: reading email on yahoo.com I clicked a NetBSD subgroup, and Konqueror crashed. I'm running Fedora 18 now. -- Backtrace (Reduced): #5 0x000000391d4bc3fe in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /lib64/libQtCore.so.4 #6 0x00000031da4799f2 in QNetworkRequest::setOriginatingObject(QObject*) () from /lib64/libQtNetwork.so.4 #7 0x00000031e0f0abd1 in WebCore::ResourceRequest::toNetworkRequest(QObject*) const () from /lib64/libQtWebKit.so.4 #8 0x00000031e0f0f62c in WebCore::QNetworkReplyHandler::redirect(WebCore::ResourceResponse&, QUrl const&) () from /lib64/libQtWebKit.so.4 #9 0x00000031e0f10320 in WebCore::QNetworkReplyHandler::sendResponseIfNeeded() () from /lib64/libQtWebKit.so.4
Created attachment 80115 [details] New crash information added by DrKonqi konqueror (4.10.3) on KDE Platform 4.10.3 using Qt 4.8.4 - What I was doing when the application crashed: I've tried to download file from some filesharing site; the link opened in a new window as plaintext instead of offering to download a zip archive, so I retried to click the link and it crashed. -- Backtrace (Reduced): #6 operator QtSharedPointer::ExternalRefCountData* (this=0x80) at ../../src/corelib/thread/qbasicatomic.h:169 #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=0x51c57d0) at tools/qsharedpointer.cpp:1255 #8 0x00000032be4799f2 in QWeakPointer<QObject> (ptr=0x51c57d0, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0x51c57d0, this=0x2fc63a0) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7fff95ee0f50, object=0x51c57d0) at access/qnetworkrequest.cpp:565
*** Bug 320404 has been marked as a duplicate of this bug. ***
What distros are you all using, Fedora ? None of these seem to be reproducible crashes and I am curious to see if the issue is isolated to a single distro. For the record there is no reliable method listed on how to reproduce this crash.
Dawit Alemayehu: I was using Fedora. I normally use Gnome / Firefox. But it was crashing a lot, so I tried to switch to KDE / Konqueror to avoid that. The main problem that I was hitting was in Gnome was: https://bugs.freedesktop.org/show_bug.cgi?id=61182 This bug also hits KDE (Kwin), but I don't think that it is the cause of our Konqueror crash. I haven't used Konqueror much and so I haven't hit this Konqueror bug again.
(In reply to comment #9) > What distros are you all using, Fedora ? yes, Fedora > None of these seem to be reproducible crashes ... I've just spent 10 minutes browsing my history and trying to click/ctrl+click every here and there on the sites I was opening when it crashed without any "luck" ... but I've upgraded to F19 meanwhile if that matters (but ... the same KDE 4.10.3 and Qt 4.8.4)
Created attachment 80682 [details] New crash information added by DrKonqi konqueror (4.10.4) on KDE Platform 4.10.4 using Qt 4.8.4 - What I was doing when the application crashed: I've just tried to reload a window where I had some youtube playlist opened. -- Backtrace (Reduced): #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x1b3c020) at tools/qsharedpointer.cpp:1257 #8 0x000000351847a683 in QWeakPointer<QObject> (ptr=0x1b3c020, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0x1b3c020, this=0x195a2e0) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7ffffe7f8880, object=0x1b3c020) at access/qnetworkrequest.cpp:565 #11 0x00000033327416d4 in WebCore::ResourceRequest::toNetworkRequest () from /lib64/libQtWebKit.so.4
*** Bug 322293 has been marked as a duplicate of this bug. ***
*** Bug 322927 has been marked as a duplicate of this bug. ***
Created attachment 81946 [details] New crash information added by DrKonqi konqueror (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.5 - What I was doing when the application crashed: I've just clicked a next link to read another page of an article on some web ... I add this just to update the version information, yes, it crashes with 4.10.5 too. -- Backtrace (Reduced): #6 operator QtSharedPointer::ExternalRefCountData* (this=0x80) at ../../src/corelib/thread/qbasicatomic.h:169 #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x6326ef0) at tools/qsharedpointer.cpp:1255 #8 0x00000036aba7a683 in QWeakPointer<QObject> (ptr=0x6326ef0, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0x6326ef0, this=0x76c27a0) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7fff3692ac60, object=0x6326ef0) at access/qnetworkrequest.cpp:565
*** Bug 323033 has been marked as a duplicate of this bug. ***
*** Bug 325146 has been marked as a duplicate of this bug. ***
*** Bug 323266 has been marked as a duplicate of this bug. ***
*** Bug 325148 has been marked as a duplicate of this bug. ***
*** Bug 322706 has been marked as a duplicate of this bug. ***
*** Bug 325823 has been marked as a duplicate of this bug. ***
*** Bug 326545 has been marked as a duplicate of this bug. ***
*** Bug 326808 has been marked as a duplicate of this bug. ***
*** Bug 326936 has been marked as a duplicate of this bug. ***
*** Bug 327187 has been marked as a duplicate of this bug. ***
*** Bug 327188 has been marked as a duplicate of this bug. ***
Created attachment 83376 [details] New crash information added by DrKonqi konqueror (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.5 - What I was doing when the application crashed: It crashed in the background, I was reading email in Trojitá when I got DrKonqi report about Konqueror crashing ... Just to update version, 4.11.2 on Fedora 19. -- Backtrace (Reduced): #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0xa79820) at tools/qsharedpointer.cpp:1257 #8 0x00000035efa7a683 in QWeakPointer<QObject> (ptr=0xa79820, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0xa79820, this=0x348e170) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7fff31575d00, object=0xa79820) at access/qnetworkrequest.cpp:565 #11 0x0000003b66f441e4 in WebCore::ResourceRequest::toNetworkRequest(WebCore::NetworkingContext*) const () from /lib64/libQtWebKit.so.4
We do not need more backtraces. We need: - QtWebKit version - steps to reproduce
Version: 4.8.4+2.2.0-3.5.1 Source Package: libQtWebKit4-4.8.4+2.2.0-3.5.1 OpenSuSE 12.3 Can I help any other way? Cheers, Terry. On Fri, Nov 8, 2013 at 6:44 AM, Christoph Feck <christoph@maxiom.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=317475 > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |christoph@maxiom.de > > --- Comment #28 from Christoph Feck <christoph@maxiom.de> --- > We do not need more backtraces. We need: > - QtWebKit version > - steps to reproduce > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
Reference comment #26 My QtWebKit version is: CODE --------- libQtWebKit4-debuginfo-4.8.5+2.3.3-91.1.x86_64 libQtWebKit4-4.8.5+2.3.3-91.1.x86_64 ----------- Problem has not returned since last update to 4.11.3. Russ
*** Bug 321076 has been marked as a duplicate of this bug. ***
I got here by way of bug 326936. ymail would ask me to upgrade my firefox or safari. I told it to continue without upgrading. It crashed konqueror instead. From strace, I gather there was a call or jump to zero. The computer is a DakTEch Freedom 4 P4 DDR System. The system board is a D865GBFL w/LAN,audio & video Processor Intel Pentium 4 3.2 Ghz 800FSB I got it in 2006. It's running CentOS 6.4 .
Steps to reproduce: 1. Select context menu on a link 2. Select "Open in a new tab" 3. Konqueror crashes I don't know how to get my current QtWebkit version and have no way of knowing what it was when I reported that the crash occured. I generally use Firefox as a web browser, so I can't recall exactly when the last crash was. These questions are mainly thought-provoking, rhetorical and intended for the program writers: Shouldn't backtrace ideally pick up things like the QtWebkit version using the debug symbols? If it does not, is there not a way to include whatever is necessary with the corresponding debug package? Yes, I realize that distributors like Ubuntu change packages so that there is no way to guarantee what is in the source ends up in the debug package. How many crash reports does it take to confirm a bug? Shouldn't the reports from this and the duplicates be sufficient?
(In reply to comment #33) > Steps to reproduce: > 1. Select context menu on a link > 2. Select "Open in a new tab" > 3. Konqueror crashes > > I don't know how to get my current QtWebkit version and have no way of > knowing what it was when I reported that the crash occured. I generally use > Firefox as a web browser, so I can't recall exactly when the last crash was. From Command Line Code -------------- @linux-rpl7:~> rpm -qa |grep libQtWebKit4 ------------- Results on openSUSE 12.3 libQtWebKit4-4.8.5+2.3.3-91.1.x86_64 libQtWebKit4-debuginfo-4.8.5+2.3.3-91.1.x86_64 > > These questions are mainly thought-provoking, rhetorical and intended for > the program writers: Shouldn't backtrace ideally pick up things like the > QtWebkit version using the debug symbols? If it does not, is there not a way > to include whatever is necessary with the corresponding debug package? Yes, > I realize that distributors like Ubuntu change packages so that there is no > way to guarantee what is in the source ends up in the debug package. How > many crash reports does it take to confirm a bug? Shouldn't the reports from > this and the duplicates be sufficient?
This is interesting, when I run this command: " rpm -qa |grep libQtWebKit4 " This is the result I get: " error: rpmdbNextIterator: skipping h# 11963 Header V3 RSA/SHA256 Signature, key ID 3dbdc284: BAD " Probably not related anyway... I using OpenSuSE 13.1 On Fri, Dec 6, 2013 at 12:18 PM, Russ Fineman <upscope@nwi.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=317475 > > --- Comment #34 from Russ Fineman <upscope@nwi.net> --- > (In reply to comment #33) > > Steps to reproduce: > > 1. Select context menu on a link > > 2. Select "Open in a new tab" > > 3. Konqueror crashes > > > > I don't know how to get my current QtWebkit version and have no way of > > knowing what it was when I reported that the crash occured. I generally > use > > Firefox as a web browser, so I can't recall exactly when the last crash > was. > From Command Line > Code > -------------- > @linux-rpl7:~> rpm -qa |grep libQtWebKit4 > ------------- > Results on openSUSE 12.3 > libQtWebKit4-4.8.5+2.3.3-91.1.x86_64 > libQtWebKit4-debuginfo-4.8.5+2.3.3-91.1.x86_64 > > > > These questions are mainly thought-provoking, rhetorical and intended for > > the program writers: Shouldn't backtrace ideally pick up things like the > > QtWebkit version using the debug symbols? If it does not, is there not a > way > > to include whatever is necessary with the corresponding debug package? > Yes, > > I realize that distributors like Ubuntu change packages so that there is > no > > way to guarantee what is in the source ends up in the debug package. How > > many crash reports does it take to confirm a bug? Shouldn't the reports > from > > this and the duplicates be sufficient? > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
From Yast: Version: 4.8.5+2.3.3-2.6.1 Installed: 4.8.5+2.3.3-2.6.1 Source Package: libQtWebKit4-4.8.5+2.3.3-2.6.1 On Sat, Dec 7, 2013 at 2:52 PM, Terry Wendt <silicon.penguin67@gmail.com>wrote: > This is interesting, when I run this command: " rpm -qa |grep > libQtWebKit4 " > > This is the result I get: " error: rpmdbNextIterator: skipping h# 11963 > Header V3 RSA/SHA256 Signature, key ID 3dbdc284: BAD " > Probably not related anyway... > > I using OpenSuSE 13.1 > > > > On Fri, Dec 6, 2013 at 12:18 PM, Russ Fineman <upscope@nwi.net> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=317475 >> >> --- Comment #34 from Russ Fineman <upscope@nwi.net> --- >> (In reply to comment #33) >> > Steps to reproduce: >> > 1. Select context menu on a link >> > 2. Select "Open in a new tab" >> > 3. Konqueror crashes >> > >> > I don't know how to get my current QtWebkit version and have no way of >> > knowing what it was when I reported that the crash occured. I generally >> use >> > Firefox as a web browser, so I can't recall exactly when the last crash >> was. >> From Command Line >> Code >> -------------- >> @linux-rpl7:~> rpm -qa |grep libQtWebKit4 >> ------------- >> Results on openSUSE 12.3 >> libQtWebKit4-4.8.5+2.3.3-91.1.x86_64 >> libQtWebKit4-debuginfo-4.8.5+2.3.3-91.1.x86_64 >> > >> > These questions are mainly thought-provoking, rhetorical and intended >> for >> > the program writers: Shouldn't backtrace ideally pick up things like the >> > QtWebkit version using the debug symbols? If it does not, is there not >> a way >> > to include whatever is necessary with the corresponding debug package? >> Yes, >> > I realize that distributors like Ubuntu change packages so that there >> is no >> > way to guarantee what is in the source ends up in the debug package. How >> > many crash reports does it take to confirm a bug? Shouldn't the reports >> from >> > this and the duplicates be sufficient? >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. >> > >
*** Bug 328634 has been marked as a duplicate of this bug. ***
*** Bug 328581 has been marked as a duplicate of this bug. ***
*** Bug 328915 has been marked as a duplicate of this bug. ***
*** Bug 329061 has been marked as a duplicate of this bug. ***
*** Bug 329198 has been marked as a duplicate of this bug. ***
*** Bug 331445 has been marked as a duplicate of this bug. ***
*** Bug 331598 has been marked as a duplicate of this bug. ***
*** Bug 331792 has been marked as a duplicate of this bug. ***
*** Bug 332418 has been marked as a duplicate of this bug. ***
*** Bug 332608 has been marked as a duplicate of this bug. ***
*** Bug 333633 has been marked as a duplicate of this bug. ***
*** Bug 333940 has been marked as a duplicate of this bug. ***
*** Bug 333783 has been marked as a duplicate of this bug. ***
*** Bug 334252 has been marked as a duplicate of this bug. ***
*** Bug 334745 has been marked as a duplicate of this bug. ***
*** Bug 336068 has been marked as a duplicate of this bug. ***
Created attachment 87522 [details] New crash information added by DrKonqi konqueror (4.12.5) on KDE Platform 4.12.5 using Qt 4.8.6 - What I was doing when the application crashed: Browsing a Dog-Forum and just clicked on a link in order to open a post. -- Backtrace (Reduced): #6 operator QtSharedPointer::ExternalRefCountData* (this=0x31ad) at ../../src/corelib/thread/qbasicatomic.h:169 #7 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x1da6ea0) at tools/qsharedpointer.cpp:1255 #8 0x000000384087d2f3 in QWeakPointer<QObject> (ptr=0x1da6ea0, this=<optimized out>) at ../../src/corelib/tools/qsharedpointer_impl.h:595 #9 operator=<QObject> (ptr=0x1da6ea0, this=0x394df00) at ../../src/corelib/tools/qsharedpointer_impl.h:600 #10 QNetworkRequest::setOriginatingObject (this=0x7fff199ea090, object=0x1da6ea0) at access/qnetworkrequest.cpp:565
*** Bug 337139 has been marked as a duplicate of this bug. ***
*** Bug 337157 has been marked as a duplicate of this bug. ***
*** Bug 337577 has been marked as a duplicate of this bug. ***
*** Bug 340308 has been marked as a duplicate of this bug. ***
*** Bug 341588 has been marked as a duplicate of this bug. ***
*** Bug 340528 has been marked as a duplicate of this bug. ***
*** Bug 345410 has been marked as a duplicate of this bug. ***
*** Bug 347274 has been marked as a duplicate of this bug. ***
*** Bug 348715 has been marked as a duplicate of this bug. ***
*** Bug 349515 has been marked as a duplicate of this bug. ***
*** Bug 350700 has been marked as a duplicate of this bug. ***
*** Bug 350812 has been marked as a duplicate of this bug. ***
*** Bug 350926 has been marked as a duplicate of this bug. ***
*** Bug 353230 has been marked as a duplicate of this bug. ***
*** Bug 353484 has been marked as a duplicate of this bug. ***
*** Bug 355369 has been marked as a duplicate of this bug. ***
*** Bug 358796 has been marked as a duplicate of this bug. ***
Thank you for the reports. As it has been a while since a duplicate was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Am 04.12.20 um 06:13 schrieb Justin Zobel: > https://bugs.kde.org/show_bug.cgi?id=317475 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > CC| |justin.zobel@gmail.com > Resolution|--- |WAITINGFORINFO > > --- Comment #71 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for the reports. > > As it has been a while since a duplicate was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked as > resolved. > > I have set the bug status to "needsinfo" pending your response, please change > back to "reported" or "resolved/worksforme" when you respond, thank you. > I can not test it, because I use a different Distro !
A quick test on 20.08.3 on Fedora 32 (go to www.google.com, search on 'monolith', right click on first result, choose 'open in new tab') does not cause a crash.
Created attachment 133876 [details] attachment-13291-0.html Since this is so old, why is it still active? Close the bloody ticket! jdg On Fri, Dec 4, 2020 at 6:49 AM Stefan Gies <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=317475 > > --- Comment #72 from Stefan Gies <sgies1963@t-online.de> --- > Am 04.12.20 um 06:13 schrieb Justin Zobel: > > https://bugs.kde.org/show_bug.cgi?id=317475 > > > > Justin Zobel <justin.zobel@gmail.com> changed: > > > > What |Removed |Added > > > ---------------------------------------------------------------------------- > > Status|REPORTED |NEEDSINFO > > CC| |justin.zobel@gmail.com > > Resolution|--- |WAITINGFORINFO > > > > --- Comment #71 from Justin Zobel <justin.zobel@gmail.com> --- > > Thank you for the reports. > > > > As it has been a while since a duplicate was reported, can you please > test and > > confirm if this issue is still occurring or if this bug report can be > marked as > > resolved. > > > > I have set the bug status to "needsinfo" pending your response, please > change > > back to "reported" or "resolved/worksforme" when you respond, thank you. > > > I can not test it, because I use a different Distro ! > > -- > You are receiving this mail because: > You are on the CC list for the bug. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
(In reply to jgrisetti from comment #74) > Created attachment 133876 [details] > attachment-13291-0.html > > Since this is so old, why is it still active? > Close the bloody ticket! > jdg Some bugs can last for many years without fixes as developer time is often stretched between many projects. I'm not sure users would like it if we just closed their tickets as they were old if the issue still existed.
(In reply to Justin Zobel from comment #75) > I'm not sure users would like it if we just closed their tickets as they > were old if the issue still existed. however, seeing how long some bugs exist unattended, it doesn't make the situation any better (yes, I'm guilty too ...) I believe this one should be closed, as the crash happened with WebKit, which is no longer in use, it has been replaced with WebEngine, so any possible fix is irrelevant in current versions
Created attachment 133918 [details] attachment-4108-0.html Resolved Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: kavol <bugzilla_noreply@kde.org> Sent: Monday, December 7, 2020 5:11:23 AM To: rbryan112@outlook.com <rbryan112@outlook.com> Subject: [kwebkitpart] [Bug 317475] Konqueror segfault opening link in new tab https://bugs.kde.org/show_bug.cgi?id=317475 --- Comment #76 from kavol <kavol@seznam.cz> --- (In reply to Justin Zobel from comment #75) > I'm not sure users would like it if we just closed their tickets as they > were old if the issue still existed. however, seeing how long some bugs exist unattended, it doesn't make the situation any better (yes, I'm guilty too ...) I believe this one should be closed, as the crash happened with WebKit, which is no longer in use, it has been replaced with WebEngine, so any possible fix is irrelevant in current versions -- You are receiving this mail because: You are on the CC list for the bug.
Created attachment 133922 [details] attachment-16715-0.html I concur! Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone -------- Original message -------- From: kavol <bugzilla_noreply@kde.org> Date: 12/7/20 04:11 (GMT-08:00) To: jgrisetti@gmail.com Subject: [kwebkitpart] [Bug 317475] Konqueror segfault opening link in new tab https://bugs.kde.org/show_bug.cgi?id=317475--- Comment #76 from kavol <kavol@seznam.cz> ---(In reply to Justin Zobel from comment #75)> I'm not sure users would like it if we just closed their tickets as they> were old if the issue still existed.however, seeing how long some bugs exist unattended, it doesn't make thesituation any better (yes, I'm guilty too ...)I believe this one should be closed, as the crash happened with WebKit, whichis no longer in use, it has been replaced with WebEngine, so any possible fixis irrelevant in current versions-- You are receiving this mail because:You are on the CC list for the bug.
I'll mark this as resolved as it is a very old bug. If anyone is still experiencing issues please reopen. Thanks for all the reports.