Bug 323571 - Juk crashes when closing
Summary: Juk crashes when closing
Status: RESOLVED DUPLICATE of bug 323441
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.6-git
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-08-15 23:17 UTC by Markus
Modified: 2013-08-23 14:26 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus 2013-08-15 23:17:51 UTC
Application: juk (3.10)
KDE Platform Version: 4.11.60
Qt Version: 4.8.6
Operating System: Linux 3.8.0-27-generic i686
Distribution: Ubuntu 13.04

-- Information about the crash:
Juk crashes every time I close it. It does not matter wether music is played or not. A Juk process is still alive and consuming ressources:

2196  9.5  3.2 237696 33448 ?        Tl   01:09   0:38 /opt/project-neon/bin/juk -caption JuK --icon juk

The crash can be reproduced every time.

-- Backtrace:
Application: JuK (juk), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb3e91a80 (LWP 2196))]

Thread 2 (Thread 0xae2e7b40 (LWP 2199)):
#0  0xb76fd424 in __kernel_vsyscall ()
#1  0xb5069dcb in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb4d99d16 in poll (__timeout=-1, __nfds=2, __fds=0xa9900b10) at /usr/include/i386-linux-gnu/bits/poll2.h:46
#3  poll_func (ufds=0xa9900b10, nfds=2, timeout=-1, userdata=0x94cd918) at pulse/thread-mainloop.c:69
#4  0xb4d8808a in pa_mainloop_poll (m=m@entry=0x94cdd10) at pulse/mainloop.c:854
#5  0xb4d888c9 in pa_mainloop_iterate (m=m@entry=0x94cdd10, block=block@entry=1, retval=retval@entry=0x0) at pulse/mainloop.c:936
#6  0xb4d889a4 in pa_mainloop_run (m=0x94cdd10, retval=retval@entry=0x0) at pulse/mainloop.c:954
#7  0xb4d99c9e in thread (userdata=0x9550b00) at pulse/thread-mainloop.c:88
#8  0xb457deaa in internal_thread_func (userdata=0x9544820) at pulsecore/thread-posix.c:83
#9  0xb4dbad78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#10 0xb50793de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb3e91a80 (LWP 2196)):
[KCrash Handler]
#7  0xb73fa53f in Phonon::AudioOutputPrivate::aboutToDeleteBackendObject (this=0x9552a48) at /build/buildd/project-neon-phonon-2+git20130808+r2796/phonon/audiooutput.cpp:285
#8  0xb7414142 in Phonon::MediaNodePrivate::deleteBackendObject (this=0x9552a48) at /build/buildd/project-neon-phonon-2+git20130808+r2796/phonon/medianode.cpp:78
#9  0xb7403291 in Phonon::FactoryPrivate::~FactoryPrivate (this=0x9285418, __in_chrg=<optimized out>) at /build/buildd/project-neon-phonon-2+git20130808+r2796/phonon/factory.cpp:235
#10 0xb74033c1 in Phonon::FactoryPrivate::~FactoryPrivate (this=0x9285418, __in_chrg=<optimized out>) at /build/buildd/project-neon-phonon-2+git20130808+r2796/phonon/factory.cpp:245
#11 0xb740261b in destroy () at /build/buildd/project-neon-phonon-2+git20130808+r2796/phonon/factory.cpp:85
#12 0xb61dd3be in qt_call_post_routines () at kernel/qcoreapplication.cpp:298
#13 0xb5427eeb in QApplication::~QApplication (this=0xbfbce060, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1111
#14 0xb6908add in KApplication::~KApplication (this=0xbfbce060, __in_chrg=<optimized out>) at /build/buildd/project-neon-kdelibs-2+git20130814+r92269~96db01c/kdeui/kernel/kapplication.cpp:894
#15 0xb6910139 in KUniqueApplication::~KUniqueApplication (this=0xbfbce060, __in_chrg=<optimized out>) at /build/buildd/project-neon-kdelibs-2+git20130814+r92269~96db01c/kdeui/kernel/kuniqueapplication.cpp:347
#16 0x080c0164 in main (argc=5, argv=0xbfbce134) at /build/buildd/project-neon-juk-2+git20130724+r2399/main.cpp:104

The reporter indicates this bug may be a duplicate of or related to bug 323441.

Possible duplicates by query: bug 323441.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-08-23 14:26:27 UTC
See https://bugs.kde.org/show_bug.cgi?id=323441#c2

*** This bug has been marked as a duplicate of bug 323441 ***