Dolphin browser will occasionally freeze

I notice this especially in the usb flash drive, when i put my mouse over a pdf file with many pages (over 9mb in size)

edit: i can confirm this also happens in other places besides the flash drive area. When i put my mouse over a large pdf file it dolphin will hang up for around 3 to 5 seconds.

Also gota fatal error

A Fatal Error Occurred
The application Dolphin (dolphin) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at Useful details include how to reproduce the error, documents that were loaded, etc.

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

e?1034h(no debugging symbols found)
[Thread debugging using libthread_db enabled]
0x00007febde8c1ce1 in nanosleep () from /lib64/
[Current thread is 1 (Thread 0x7febe2fde750 (LWP 27917))]

Thread 1 (Thread 0x7febe2fde750 (LWP 27917)):
#0 0x00007febde8c1ce1 in nanosleep () from /lib64/
#1 0x00007febde8c1adc in sleep () from /lib64/
#2 0x00007febe0fc460f in ?? () from /usr/lib64/
#3 0x00007febe0fc4f6a in KCrash::defaultCrashHandler(int) () from /usr/lib64/
#4 <signal handler called>
#5 0x00007febe2886903 in KFileItem::isDir() const () from /usr/lib64/
#6 0x00007febe2878c96 in ?? () from /usr/lib64/
#7 0x00007febe2879c80 in ?? () from /usr/lib64/
#8 0x00007febe287a0ae in KDirModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/
#9 0x00007febdf66a454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/
#10 0x00007febe2860ab5 in KDirLister::itemsDeleted(KFileItemList const&) () from /usr/lib64/
#11 0x00007febe2861721 in KDirLister::Private::emitItemsDeleted(KFileItemList const&) () from /usr/lib64/
#12 0x00007febe286a728 in ?? () from /usr/lib64/
#13 0x00007febe286af29 in ?? () from /usr/lib64/
#14 0x00007febe286b384 in ?? () from /usr/lib64/
#15 0x00007febe2870ec4 in ?? () from /usr/lib64/
#16 0x00007febdf66a454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/
#17 0x00007febe287b1f5 in OrgKdeKDirNotifyInterface::FilesRemoved(QStringList const&) () from /usr/lib64/
#18 0x00007febe287b374 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/
#19 0x00007febe04744cf in ?? () from /usr/lib64/
#20 0x00007febe047b61f in ?? () from /usr/lib64/
#21 0x00007febdf665105 in QObject::event(QEvent*) () from /usr/lib64/
#22 0x00007febdfad31bd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/
#23 0x00007febdfadaf8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/
#24 0x00007febe0f621db in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/
#25 0x00007febdf656091 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/
#26 0x00007febdf656d3a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/
#27 0x00007febdf67e863 in ?? () from /usr/lib64/
#28 0x00007febdb7f50fb in g_main_context_dispatch () from /usr/lib64/
#29 0x00007febdb7f88cd in ?? () from /usr/lib64/
#30 0x00007febdb7f8a8b in g_main_context_iteration () from /usr/lib64/
#31 0x00007febdf67e4ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/
#32 0x00007febdfb639bf in ?? () from /usr/lib64/
#33 0x00007febdf6549a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/
#34 0x00007febdf654b2d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/
#35 0x00007febdf656ffd in QCoreApplication::exec() () from /usr/lib64/
#36 0x0000000000441fbd in _start ()

Anyone know?

out of curiosity which version of kde and dolphin are you using? i used to see the same behavior in kde4.0 but haven’t seen it since switching to kde4.1

Im using kde 4.2.2 and dolphin 1.2.1

I wish I could help, I’ve seen this behavior in 4.1 and 4.2 when I try to open a video in my windows partition or a .mp4 file anywhere. Dolphin would become unresponsive for about 15 seconds then it would work normally. I haven’t had the problem in 4.3 yet (knock on wood).

Here’s the bug report