Version: (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages I was using Konqueror on KDE 4.1.3 and it suddenly crashed (maybe because of the number of tabs opened). When I tried to restore the session it crashed again and again except when I closed one tab while loading.
Did you get any backtrace for the KDE Crash Handler? And was it a specific URL that caused a problem and which we could revisit ourselve to reproduce the problem?
Created attachment 28511 [details] Kcrash report
(In reply to comment #1) > Did you get any backtrace for the KDE Crash Handler? And was it a specific URL > that caused a problem and which we could revisit ourselve to reproduce the > problem? > I submitted the report. The URL visited are of the form : http://fr.finance.yahoo.com/q/hp?s=ALO.PA&b=1&a=00&c=2008&e=12&d=10&f=2008&g=m (with several different values for s=XXXXX) and : http://fr.finsearch.yahoo.com/fr/index.php?s=fr_sort&nm=alstom&tp=S&r=*&sub=Recherche+ Hope this helps...
(paste of above backtrace follows) [Thread debugging using libthread_db enabled] [New Thread 0xb60406c0 (LWP 9811)] [KCrash handler] #6 0xb7e3ee68 in ?? () from /lib/tls/i686/cmov/libc.so.6 #7 0xb7e3f456 in free () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7365f2d in qFree () from /usr/lib/libQtCore.so.4 #9 0xb75ad14b in ~KFilterDev (this=0x2018) at /usr/include/qt4/QtCore/qbytearray.h:364 #10 0xb40fea5f in ~KHTMLPageCacheEntry (this=0xa7a3190) at /build/buildd/kde4libs-4.1.3/khtml/khtml_pagecache.cpp:94 #11 0xb40ffd1a in KHTMLPageCache::createCacheEntry (this=0xa17b860) at /build/buildd/kde4libs-4.1.3/khtml/khtml_pagecache.cpp:158 #12 0xb40aeb5e in KHTMLPart::slotData (this=0xa490388, kio_job=0xa4d7890, data=@0xbfe38a94) at /build/buildd/kde4libs-4.1.3/khtml/khtml_part.cpp:1592 #13 0xb40d3b97 in KHTMLPart::qt_metacall (this=0xa490388, _c=QMetaObject::InvokeMetaMethod, _id=19, _a=0xbfe387e8) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/khtml/khtml_part.moc:264 #14 0xb7470a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb74717e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7b847a9 in KIO::TransferJob::data (this=0xa4d7890, _t1=0xa4d7890, _t2=@0xbfe38a94) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/jobclasses.moc:356 #17 0xb7b85142 in KIO::TransferJob::slotData (this=0xa4d7890, _data=@0xbfe38a94) at /build/buildd/kde4libs-4.1.3/kio/kio/job.cpp:927 #18 0xb7b93115 in KIO::TransferJob::qt_metacall (this=0xa4d7890, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfe3890c) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/jobclasses.moc:337 #19 0xb7470a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #20 0xb74717e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #21 0xb7c52043 in KIO::SlaveInterface::data (this=0x9f1cf58, _t1=@0xbfe38a94) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/slaveinterface.moc:136 #22 0xb7c55cbc in KIO::SlaveInterface::dispatch (this=0x9f1cf58, _cmd=100, rawdata=@0xbfe38a94) at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:162 #23 0xb7c526a7 in KIO::SlaveInterface::dispatch (this=0x9f1cf58) at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:90 #24 0xb7c426cd in KIO::Slave::gotInput (this=0x9f1cf58) at /build/buildd/kde4libs-4.1.3/kio/kio/slave.cpp:322 #25 0xb7c45113 in KIO::Slave::qt_metacall (this=0x9f1cf58, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe38ba8) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/slave.moc:75 #26 0xb7470a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #27 0xb74717e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #28 0xb7b528f7 in KIO::Connection::readyRead (this=0xa61d8a8) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/connection.moc:84 #29 0xb7b549c9 in KIO::ConnectionPrivate::dequeue (this=0xa7af508) at /build/buildd/kde4libs-4.1.3/kio/kio/connection.cpp:82 #30 0xb7b54b56 in KIO::Connection::qt_metacall (this=0xa61d8a8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xb1d9ce0) at /build/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kio/connection.moc:72 #31 0xb7469bfb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #32 0xb746b771 in QObject::event () from /usr/lib/libQtCore.so.4 #33 0xb695f8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #34 0xb696776e in QApplication::notify () from /usr/lib/libQtGui.so.4 #35 0xb792bb2d in KApplication::notify (this=0xbfe39524, receiver=0xa61d8a8, event=0xa85c818) at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311 #36 0xb745be61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #37 0xb745cae5 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #38 0xb745ccdd in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #39 0xb748682f in ?? () from /usr/lib/libQtCore.so.4 #40 0xb63d26f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #41 0xb63d5da3 in ?? () from /usr/lib/libglib-2.0.so.0 #42 0xb63d5f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #43 0xb7486478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #44 0xb69f9ee5 in ?? () from /usr/lib/libQtGui.so.4 #45 0xb745a52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #46 0xb745a6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #47 0xb745cda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #48 0xb695f767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #49 0xb7ff12ed in kdemain () from /usr/lib/libkdeinit4_konqueror.so #50 0x080485b2 in _start () #0 0xb8039430 in __kernel_vsyscall () rtavenar: If you put the backtrace directly into the bugreport, it comes up in searches. Thanks!
Thanks for the report. If the bug is still reproducible (e.g. you still have that session file) you can help us enormously by running the crashing session in valgrind, e.g. by doing: valgrind konqueror &> log in a shell, and following the restoration sequence to get it to crash. The log file will likely have lines starting with == that will contain good analysis of the crash. To elaborate a bit, I've seen this bug myself, but never in a reproducible way, which makes it close to impossible to fix...
Might be the same issue as bug 157706 (and duplicates). AFAIK, no reporter found a way to reproduce it so far :-(
Created attachment 28538 [details] Log generated by valgrind I have a log file here produced using valgrind. I just hope that the fact that I was closing another instance of Konqueror when the "interesting" instance crashed has not impaired valgrind analysis...
Unfortunately that has nothing interesting :( *** This bug has been marked as a duplicate of bug 157706 ***