Version: (using KDE 4.2.4) OS: Linux Installed from: Unlisted Binary Package When one tries to click on a large .mp4 video file >400Mbyte. Dolphin starts eating up all RAM memory + Swap space. After this the computer is really slow. Killing Dolphin frees up the memory and one can continue to work. How to reproduce: Click on a >400 Mbyte .mp4 file to make Dolphin to start and preview the file. Expected Behaviour: All RAM and finally all Swap space going to be allocated by Dolphin. Thus making the Computer really slow. Test file: http://www.podtrac.com/pts/redirect.mp4/bitcast-a.bitgravity.com/revision3/web/hak5/0516/hak5--0516--fourtytwo--hd.h264.mp4
Thanks for the report, this has been fixed in Dolphin for KDE 4.3.
ok, Thanks
I confirm the bug in Dolphin (except for the swap: I don't remember seeing it eat up the swap), and also in Konqueror (KDE 4.2.2). Is it or will it also be fixed in Konqueror (KDE 4.3)?
@Grasyop: In Konqueror the issue should not occur, as it does not have an Information Panel. Do you have tooltips enabled?
Peter Penz, Sorry, the bug appears in Konqueror when you right-click the file and ask for its properties.
@Grasyop: The root cause is in this case the strigi analyzer for MP4s, which is used for the properties dialog. I cannot reproduce the issue with the properties dialog in KDE 4.3 and a recent strigi version (tested with Dolphin and Konqueror with huge MP4 files). If the issue still occurs with the properties dialog when KDE 4.3 gets released, please reopen a new report as this is out of scope of Dolphin and must be reassigned to strigi (or maybe kdelibs). Thanks!
*** Bug 197953 has been marked as a duplicate of this bug. ***
I can confirm this is still a bug with KDE 4.3.0 (Dolphin v1.3). Apparently I don't have enough packages installed to provide useful information (!), but I did grab this.. Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007f450a8d611b in memcpy () from /lib/libc.so.6 #6 0x00007f450b45239d in QIODevice::read () from /usr/lib/libQtCore.so.4 #7 0x00007f450ed0d0a4 in ?? () from /usr/lib/libkio.so.5 #8 0x00007f450ed0faba in ?? () from /usr/lib/libkio.so.5 #9 0x00007f450ed0fbb5 in ?? () from /usr/lib/libkio.so.5 #10 0x00007f44fc99fdb0 in Mp4ThroughAnalyzer::connectInputStream () from /usr/lib/strigi/strigita_mp4.so #11 0x00007f450a4030eb in ?? () from /usr/lib/libstreamanalyzer.so.0 #12 0x00007f450ed0d967 in ?? () from /usr/lib/libkio.so.5 #13 0x00007f450ed0ef02 in KFileMetaInfo::KFileMetaInfo () from /usr/lib/libkio.so.5 #14 0x00007f450ecf7d49 in KFileItem::metaInfo () from /usr/lib/libkio.so.5 #15 0x00007f450ecfaf2d in KFileItem::getToolTipText () from /usr/lib/libkio.so.5 #16 0x00007f450e27d93d in ?? () from /usr/lib/libdolphinprivate.so.4 #17 0x00007f450e27db88 in ?? () from /usr/lib/libdolphinprivate.so.4 #18 0x00007f450b4cbea2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #19 0x00007f450b4c6263 in QObject::event () from /usr/lib/libQtCore.so.4 #20 0x00007f450b94bf4d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #21 0x00007f450b95418a in QApplication::notify () from /usr/lib/libQtGui.so.4 #22 0x00007f450ced371b in KApplication::notify () from /usr/lib/libkdeui.so.5 #23 0x00007f450b4b66ac in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #24 0x00007f450b4e3516 in ?? () from /usr/lib/libQtCore.so.4 #25 0x00007f450b4dfb2d in ?? () from /usr/lib/libQtCore.so.4 #26 0x00007f4506b3520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0x00007f4506b388e0 in ?? () from /usr/lib/libglib-2.0.so.0 #28 0x00007f4506b38a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0x00007f450b4dfa8f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #30 0x00007f450b9e4bdf in ?? () from /usr/lib/libQtGui.so.4 #31 0x00007f450b4b4f42 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #32 0x00007f450b4b5314 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #33 0x00007f450b4b75e4 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #34 0x00000000004396ed in _start () Sadly, the "merging" of this bug did not merge posts from the other bug, where further information was posted.
I can also confirm that when tooltips are disabled, there is no issue. And no tooltips!
@cor: Yes, this also indicates that it is the Strigi issue mentioned above. I've reported the issues at: http://sourceforge.net/tracker/?func=detail&aid=2830904&group_id=171000&atid=856302 http://sourceforge.net/tracker/?func=detail&aid=2830902&group_id=171000&atid=856302 For KDE 4.4 Dolphin won't use Strigi anymore in the tooltips (-> issue solved like in the Information Panel), but for sure this does not help for KDE 4.3.x :-(
*** Bug 205189 has been marked as a duplicate of this bug. ***
*** Bug 198078 has been marked as a duplicate of this bug. ***
*** Bug 221307 has been marked as a duplicate of this bug. ***
*** Bug 224907 has been marked as a duplicate of this bug. ***
*** Bug 245275 has been marked as a duplicate of this bug. ***
*** Bug 231197 has been marked as a duplicate of this bug. ***
*** Bug 243464 has been marked as a duplicate of this bug. ***
Created attachment 49927 [details] New crash information added by DrKonqi dolphin (1.5) on KDE Platform 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2)) using Qt 4.7.0 - What I was doing when the application crashed: Happens mostly while moving or browsing files. -- Backtrace (Reduced): #6 memcpy () at ../sysdeps/x86_64/memcpy.S:161 #7 0x00007f76bcc4cec0 in QIODevicePrivateLinearBuffer::read (this=<value optimized out>, data=0x2fceeb0 "\220\070V\002", maxSize=1024) at /usr/include/bits/string3.h:52 #8 QIODevice::read (this=<value optimized out>, data=0x2fceeb0 "\220\070V\002", maxSize=1024) at io/qiodevice.cpp:836 #9 0x00007f76bebb5de4 in QIODeviceInputStream::fillBuffer (this=0x7f7697705880, start=0x2fceab0 "", space=1023) at ../../kio/kio/kfilemetainfo.cpp:68 #10 0x00007f76bebb8895 in Strigi::BufferedStream<char>::writeToBuffer (this=0x7f7697705880, ntoread=1, maxread=1024) at /usr/include/strigi/bufferedstream.h:116