Bug 365796

Summary: Dolphin crash when I was copying a huge file
Product: [Applications] dolphin Reporter: Angel <angelbravosaenz>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: fritigerngothly, justin.zobel, mail
Priority: NOR Keywords: drkonqi
Version: 15.12.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Angel 2016-07-17 22:20:18 UTC
Application: dolphin (15.12.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Dolphin crash when  I drag  a big .mkv file (11.6 GB) from a 3.0 usb pendrive to a home folder for copy it. It could only copy about 135 MB until failure. I repeat and works fine.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1931b1a8c0 (LWP 10890))]

Thread 3 (Thread 0x7f1910fcd700 (LWP 10893)):
#0  0x00007f193151fe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f1927c9239c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f1927c924ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f192c309a9b in QEventDispatcherGlib::processEvents (this=0x7f190c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x00007f192c2b0dea in QEventLoop::exec (this=this@entry=0x7f1910fccd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007f192c0cd8a4 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:503
#6  0x00007f192c0d284e in QThreadPrivate::start (arg=0x160f680) at thread/qthread_unix.cpp:331
#7  0x00007f192881d6fa in start_thread (arg=0x7f1910fcd700) at pthread_create.c:333
#8  0x00007f193152bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f191cc44700 (LWP 10891)):
#0  0x00007f193151fe8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f1925c0bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f1925c0d8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f191f5c8629 in QXcbEventReader::run (this=0x11925e0) at qxcbconnection.cpp:1253
#4  0x00007f192c0d284e in QThreadPrivate::start (arg=0x11925e0) at thread/qthread_unix.cpp:331
#5  0x00007f192881d6fa in start_thread (arg=0x7f191cc44700) at pthread_create.c:333
#6  0x00007f193152bb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f1931b1a8c0 (LWP 10890)):
[KCrash Handler]
#6  QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::data (this=0x9) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:983
#8  QObject::d_func (this=0x1) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:110
#9  QCoreApplication::notifyInternal (this=0x7ffed34f80c0, receiver=0x1, event=event@entry=0x7ffed34f7d50) at kernel/qcoreapplication.cpp:962
#10 0x00007f192c30889d in QCoreApplication::sendEvent (event=0x7ffed34f7d50, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#11 QTimerInfoList::activateTimers (this=0x11b6f80) at kernel/qtimerinfo_unix.cpp:637
#12 0x00007f192c308da1 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:177
#13 0x00007f1927c921a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f1927c92400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f1927c924ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f192c309a7f in QEventDispatcherGlib::processEvents (this=0x11be4b0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#17 0x00007f192c2b0dea in QEventLoop::exec (this=this@entry=0x7ffed34f7f90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#18 0x00007f192c2b8e8c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#19 0x00007f192c7fec3c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1542
#20 0x00007f192cdb4495 in QApplication::exec () at kernel/qapplication.cpp:2976
#21 0x00007f193184be2b in kdemain (argc=2, argv=<optimized out>) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/main.cpp:150
#22 0x00007f1931445830 in __libc_start_main (main=0x400710 <main(int, char**)>, argc=2, argv=0x7ffed34f8248, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffed34f8238) at ../csu/libc-start.c:291
#23 0x0000000000400749 in _start ()

Possible duplicates by query: bug 272970, bug 256838, bug 250516, bug 233538.

Reported using DrKonqi
Comment 1 Elvis Angelaccio 2016-12-24 14:33:53 UTC
*** Bug 372127 has been marked as a duplicate of this bug. ***
Comment 2 Julian Steinmann 2018-05-17 19:36:50 UTC
Can you still reproduce this behavior with a newer version of Dolphin? The copy process has since been improved and your crash might have been fixed in the mean time.
Comment 3 Angel 2018-05-17 20:29:53 UTC
Yes, and it's very frustrating that it doesn't crash when valgrind is working, but I keep trying.
Comment 4 Julian Steinmann 2018-05-18 15:05:57 UTC
Okay, if you do manage to get a valgrind log that would be great.
Comment 5 Justin Zobel 2020-10-25 07:17:26 UTC
Angel is this still occurring on current Dolphin versions?

If so, are you able to please provide the valgrind log as discussed, thanks.
Comment 6 Angel 2020-10-25 21:34:17 UTC
(In reply to Justin from comment #5)
> Angel is this still occurring on current Dolphin versions?
> 
> If so, are you able to please provide the valgrind log as discussed, thanks.

Never happen again. Actually, I'd already forgotten it...
Comment 7 Justin Zobel 2020-10-25 21:42:32 UTC
Thanks for retesting Angel, I'll mark this one as resolved for now, if the issue re-occurs please don't hesitate to open a new report.
Comment 8 Angel 2020-10-25 21:45:06 UTC
(In reply to Justin from comment #7)
> Thanks for retesting Angel, I'll mark this one as resolved for now, if the
> issue re-occurs please don't hesitate to open a new report.

Anytime.