picard crashed with SIGSEGV in avcodec_decode_audio2()

[David Mathers]

Binary package hint: libavcodec52

crash only happens with ogg vorbis files. happens when picard is scanning the file to create the fingerprint.

ogg vorbis file that caused this crash attached.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/picard
InterpreterPath: /usr/bin/python2.6
Package: picard 0.11-1ubuntu2
ProcCmdline: /usr/bin/python /usr/bin/picard
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: picard
Stacktrace:
 #0 0xb2fabce5 in ?? () from /usr/lib/i686/cmov/libavcodec.so.52
 #1 0xb2c87222 in avcodec_decode_audio2 ()
    from /usr/lib/i686/cmov/libavcodec.so.52
StacktraceTop:
 ?? () from /usr/lib/i686/cmov/libavcodec.so.52
 avcodec_decode_audio2 ()
Title: picard crashed with SIGSEGV in avcodec_decode_audio2()
Uname: Linux 2.6.28-11-server i686
UserGroups: adm admin audio cdrom dialout dip disk floppy lpadmin netdev plugdev powerdev sambashare scanner vboxusers video
SegvAnalysis:
 Segfault happened at: 0xb2fabce5: movdqa %xmm0,(%ebx,%ecx,1)
 PC (0xb2fabce5) ok
 source "%xmm0" ok
 destination "(%ebx,%ecx,1)" (0xae585008) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

[Apport retracing service (apport)]

StacktraceTop:float_to_int16_interleave_sse2 (dst=0xae585908,
vorbis_decode_frame (avccontext=0xa7b17f0, data=0xae585008,
avcodec_decode_audio2 (avctx=0xa7b17f0, samples=0xae585008,
?? ()
PyEval_EvalFrameEx (f=0xa7ac3c4, throwflag=0)

[Brian J. Murrell (brian-interlinx)]

This bug report is over 4 months old. Has there been any progress at all?

[Brian J. Murrell (brian-interlinx)]

Fix is at http://bazaar.launchpad.net/~musicbrainz-developers/picard/trunk/revision/947#picard/musicdns/avcodec.c

Would be nice if we could get a bugfix release in Jaunty.

[Jerry Chong (zanglang)]

Or Karmic, in that matter. Would it be possible to suggest merging the patch as linked by Brain into Ubuntu before Debian?

[Eric Casteleijn (thisfred)]

Lucid, then maybe? :)

[Eric Casteleijn (thisfred)]

Ok, I've applied the patch and am uploading it to my own ppa, if it works, I will seek sponsorship. For lucid I think we'll want to have 0.12 of picard, rather than a patched 0.11, but the fix is small and the bug so bad that I think we should backport just that fix to karmic.

[Eric Casteleijn (thisfred)]

The patched package for Lucid is in my repository and works. You can add it to your apt sources like so:

sudo add-apt-repository ppa:thisfred/ppa

and then upgrade picard. It's has a version number such that it will be automatically upgraded to any official release of the patch, or any other releases in lucid.

[Eric Casteleijn (thisfred)]

I see 0.12.1 which fixes this bug has landed in lucid. I don't know whether to mark this as fix committed/released, since lucid is still in alpha, so I'm leaving it alone, but I can confirm that the bug is finally gone in Lucid. Yay!