Version: (using KDE 3.5.9) Installed from: Gentoo Packages Compiler: GCC 4.1 Gentoo 2008 OS: Linux When viewing the Youtube Members Area (my videos) you get a "A script causes KHTML to freeze" Message, when clicking away it sometimes works and sometimes crashes! See attached Screenshot! Reproducability: Always!
Created attachment 26612 [details] proof
(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb68e16d0 (LWP 14124)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb73758d9 in QGList::findRef () from /usr/qt/3/lib/libqt-mt.so.3 #7 0xb7376a05 in QGList::removeRef () from /usr/qt/3/lib/libqt-mt.so.3 #8 0xb63578c1 in ?? () from /usr/kde/3.5/lib/libkhtml.so.4 #9 0xb70bdfa1 in QObject::event () from /usr/qt/3/lib/libqt-mt.so.3 #10 0xb705ef57 in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3 #11 0xb705fb11 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3 #12 0xb76a96fe in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4 #13 0xb70540cc in QEventLoop::activateTimers () from /usr/qt/3/lib/libqt-mt.so.3 #14 0xb700ed0c in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3 #15 0xb7075a61 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3 #16 0xb70758e6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3 #17 0xb705e9df in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3 #18 0xb67c6785 in kdemain () from /usr/kde/3.5/lib/libkdeinit_konqueror.so #19 0xb7b5e724 in kdeinitmain () from /usr/kde/3.5/lib/kde3/konqueror.so #20 0x0804ea87 in ?? () #21 0x00000004 in ?? () #22 0x080748a8 in ?? () #23 0x00000001 in ?? () #24 0x00000000 in ?? ()
Hello. Thank you for your report. Unfortunately the backtrace does not provide enough information to find the problem. Could you please install debugging packages and reproduce the problem. Instructions are provided in this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports .
*** This bug has been marked as a duplicate of 140214 ***