Bug 171943 - Crash in VolumeFaderEffectXT with xine backend
Summary: Crash in VolumeFaderEffectXT with xine backend
Status: RESOLVED WORKSFORME
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: Xine backend (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Matthias Kretz
URL:
Keywords:
: 205231 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-01 07:09 UTC by Mark Kretschmann
Modified: 2009-08-26 20:47 UTC (History)
3 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 Mark Kretschmann 2008-10-01 07:09:42 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Was playing a shoutcast stream in Amarok 2, pressed Stop, and then this ASSERT got triggered in VolumeFaderEffectXT.


Backtrace:

Thread 18 (Thread 0x42610950 (LWP 30656)):
[KCrash Handler]
#5  0x00007f33cd3a9095 in raise () from /lib/libc.so.6
#6  0x00007f33cd3aaaf0 in abort () from /lib/libc.so.6
#7  0x00007f33ceb52055 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f33ceb5219d in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f33ba1d154c in Phonon::Xine::VolumeFaderEffectXT::rewireTo (this=0x586e5f0, source=0x74dd70) at /home/mark/kde/src/kdebase/runtime/phonon/xine/volumefadereffect.cpp:193
#10 0x00007f33ba1aca9d in Phonon::Xine::XineThread::event (this=0x7bf650, e=0x4f7c870) at /home/mark/kde/src/kdebase/runtime/phonon/xine/xinethread.cpp:128
#11 0x00007f33cc37eacf in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#12 0x00007f33cc380c85 in QApplication::notify () from /usr/lib/libQtGui.so.4
#13 0x00007f33ccf3b8f8 in KApplication::notify (this=0x7fffd73bb6c0, receiver=0x7bf650, event=0x4f7c870) at /home/mark/kde/src/kdelibs/kdeui/kernel/kapplication.cpp:307
#14 0x00007f33cec3b6b9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#15 0x00007f33cec3c9db in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#16 0x00007f33cec646e3 in ?? () from /usr/lib/libQtCore.so.4
#17 0x00007f33cb6c03d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0x00007f33cb6c36e5 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x00007f33cb6c3bcb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0x00007f33cec649df in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#21 0x00007f33cec3ab35 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#22 0x00007f33cec3ac8b in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#23 0x00007f33ceb56c98 in QThread::exec () from /usr/lib/libQtCore.so.4
#24 0x00007f33ba1ac3de in Phonon::Xine::XineThread::run (this=0x7bf650) at /home/mark/kde/src/kdebase/runtime/phonon/xine/xinethread.cpp:141
#25 0x00007f33ceb59fd5 in ?? () from /usr/lib/libQtCore.so.4
#26 0x00007f33ce8d83f7 in start_thread () from /lib/libpthread.so.0
#27 0x00007f33cd44eb3d in clone () from /lib/libc.so.6
#28 0x0000000000000000 in ?? ()
Comment 1 Mark Kretschmann 2008-10-01 07:11:41 UTC
Version is SVN trunk from 28-September-2008
Comment 2 Matthias Kretz 2008-11-25 14:30:01 UTC
Is this a one-time crash or reproducible? Do you have a self-compiled/installed libxine? If you can reproduce please show me the debug output of
% PHONON_XINE_VERBOSITY=3 amarok
Comment 3 Mark Kretschmann 2008-11-26 08:22:51 UTC
No, I could never reproduce the crash. It seems to have been a one-off thing.

So feel free to disregard it, if you can't spot an obvious bug.
Comment 4 Matthias Kretz 2008-11-26 10:15:15 UTC
Alright, if somebody ever hits this one again, reopen. But generally - from the code - this failed assertion should be impossible, but perhaps there's a race condition I've overlooked.
Comment 5 Dario Andres 2009-06-20 23:19:59 UTC
Bug 197312 seems to be the same but on KDE4.2.90 / Phonon4.3.1.
@Matthias: could you take a look on it ?
Thanks
Comment 6 Mark Kretschmann 2009-08-26 20:47:53 UTC
*** Bug 205231 has been marked as a duplicate of this bug. ***