Bug 356081 - Dragon player crashes when trying to play a mp4 file from a smb share
Summary: Dragon player crashes when trying to play a mp4 file from a smb share
Status: RESOLVED WORKSFORME
Alias: None
Product: dragonplayer
Classification: Applications
Component: general (show other bugs)
Version: 2.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2015-11-29 14:42 UTC by Arnold Greving
Modified: 2018-10-27 04:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arnold Greving 2015-11-29 14:42:27 UTC
Application: dragon (2.0)
KDE Platform Version: 4.14.8
Qt Version: 4.8.6
Operating System: Linux 3.19.0-33-generic x86_64
Distribution: Ubuntu 15.04

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

I opened a mp4 movie (over the network from a smb path). The Dragon player was unable to play the movie. After hitting the close button the Dragon player crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Dragon Player (dragon), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2ed6fa7800 (LWP 6909))]

Thread 3 (Thread 0x7f2ebf689700 (LWP 6910)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00007f2ec210bf24 in ?? () from /usr/lib/nvidia-358/libGL.so.1
#2  0x00007f2ec05f7506 in ?? () from /usr/lib/nvidia-358/libnvidia-glcore.so.358.16
#3  0x00007f2ec210b53c in ?? () from /usr/lib/nvidia-358/libGL.so.1
#4  0x00007f2ed0c2a6aa in start_thread (arg=0x7f2ebf689700) at pthread_create.c:333
#5  0x00007f2ed3af5eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f2ebcae4700 (LWP 6914)):
#0  0x00007f2ed3aea8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f2ecfea3ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2ecfea3fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2ed458687e in QEventDispatcherGlib::processEvents (this=0x7f2eac005670, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007f2ed4555d21 in QEventLoop::processEvents (this=this@entry=0x7f2ebcae3d80, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f2ed4556085 in QEventLoop::exec (this=this@entry=0x7f2ebcae3d80, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f2ed4449e89 in QThread::exec (this=this@entry=0x2a2f2e0) at thread/qthread.cpp:538
#7  0x00007f2ed4536493 in QInotifyFileSystemWatcherEngine::run (this=0x2a2f2e0) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f2ed444c6ff in QThreadPrivate::start (arg=0x2a2f2e0) at thread/qthread_unix.cpp:349
#9  0x00007f2ed0c2a6aa in start_thread (arg=0x7f2ebcae4700) at pthread_create.c:333
#10 0x00007f2ed3af5eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f2ed6fa7800 (LWP 6909)):
[KCrash Handler]
#6  0x00007f2ed3a24267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007f2ed3a25eca in __GI_abort () at abort.c:89
#8  0x00007f2ed3a67c53 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f2ed3b801a8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#9  0x00007f2ed3a6fc69 in malloc_printerr (ptr=<optimized out>, str=0x7f2ed3b7c2fa "free(): invalid pointer", action=1) at malloc.c:4965
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3834
#11 0x00007f2ed3a7389c in __GI___libc_free (mem=<optimized out>) at malloc.c:2950
#12 0x00007f2ed2f0a7b5 in XrmDestroyDatabase (db=0x21d2210) at ../../src/Xrm.c:2662
#13 0x00007f2ed2ef2813 in _XFreeDisplayStructure (dpy=dpy@entry=0x21ce8f0) at ../../src/OpenDis.c:618
#14 0x00007f2ed2ee061f in XCloseDisplay (dpy=0x21ce8f0) at ../../src/ClDisplay.c:72
#15 0x00007f2ed4af8cc1 in qt_cleanup () at kernel/qapplication_x11.cpp:2774
#16 0x00007f2ed4a8a83c in QApplication::~QApplication (this=0x7ffedbc7f6d0, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1195
#17 0x000000000041921c in main (argc=<optimized out>, argv=0x7ffedbc7f7f8) at ../../../src/app/main.cpp:54

Possible duplicates by query: bug 348699, bug 347139, bug 347134, bug 347050, bug 346742.

Reported using DrKonqi
Comment 1 Harald Sitter 2015-11-30 08:47:50 UTC
From the looks of it during the normal application exit something inside libx11 hit an invalid pointer and that caused the crash. Which Phonon backend were you using at the time? Can you reproduce this crash?

Fetching additional debug information using a program called valgrind [1] would likely help finding out why exactly it crashes. If you cannot reproduce the crash I don't think we can do much about it though as the information at hand doesn't really tell us where the crash was caused.

Also, please note that Kubuntu 15.04 is going to be unsupported in 1-2 months. It might well be that 15.10 already resolves the issue.

[1] https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind
Comment 2 Arnold Greving 2015-11-30 10:31:52 UTC
The crash is reproduce-able.

I have the following phonon (AMD64) packages installed:
- phonon -> 4:4.8.3-0ubuntu2
- phonon-backend-gstreamer -> 4:4.8.2-0ubuntu1
- phonon-backend-gstreamer-common -> 4:4.8.2-0ubuntu1
- phonon4qt5-backend-gstreamer -> 4:4.8.2-0ubuntu1
Comment 3 Andrew Crouthamel 2018-09-25 21:53:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 04:08:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!