Bug 109028

Summary:	crash when pausing an MPC file and try to start it again
Product:	[Applications] amarok	Reporter:	Greg Tourte <artourter>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	1.3-beta2
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Greg Tourte 2005-07-13 16:39:32 UTC

Version:           1.3-beta2 (using KDE KDE 3.3.2)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.4 
OS:                Linux

this is using xine engine with xine-lib 1.0.1 (this is the only engine on my system that supports musepack files)

simply start playing a musepack file (.mpc), press pause and then play. it crashes every time I try on any musepack file I have.

my version of amarok is stripped so a backtrace will probably not contain any relevant info but I can give one if requested.

this might be linked to bug #99199, but these crashes are not random so I don't think it is.

Comment 1 Greg Tourte 2005-07-13 20:27:01 UTC

an addition to my bug report, the machine on which I reproduce the bug is a pentium IV with HT enabled and kernel 2.6.11.9.

I have since then tried it on a different machine with kernel 2.4.29 and no smp (single K6 II) and cannot reproduce the crash.

the xine library is the same on the same version of slackware.

Comment 2 Alexandre Oliveira 2005-08-13 02:10:08 UTC

Seems to be a bug in xine-lib, as amaroK works with all files formats the same way. Can you reproduce this with xine?

Comment 3 Greg Tourte 2005-08-15 14:48:25 UTC

no I can't. xine, on its own, works fine.

I had it suggested to me that it might have been the way xine was compiled (package straight from slackware) but I since recompiled it on the actual machine with the bog standard ./configure && make && make install and still did the same thing although not every time anymore.

I have now just updated to amarok 1.3 and xine-lib 1.0.2 and it seems more stable than xine-lib 1.0.2 (self compiled) and 1.3-beta3.

I'll keep testing. but the problem is that when it crashes it doesn't always try to send the backtrace email but hey. we'll see

Comment 4 Matt Rogers 2005-09-18 05:23:02 UTC

if you can manually generate a backtrace by running the amarokapp executible in gdb, that might be able to provide us with a backtrace. Otherwise, there won't be much that can be done.

Comment 5 Mark Kretschmann 2005-09-26 17:43:18 UTC


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