mythcommflag crashed with SIGSEGV in mpeg2_slice()

Bug #414586 reported by Jaakan Shorter
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mythtv

I was not using this computer at the time of the crash.

Description: Ubuntu 9.04
Release: 9.04

mythtv:
  Installed: 0.21.0+fixes19961-0ubuntu8
  Candidate: 0.21.0+fixes19961-0ubuntu8
  Version table:
 *** 0.21.0+fixes19961-0ubuntu8 0
        500 http://archive.ubuntu.com jaunty/multiverse Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/mythcommflag
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.21.0+fixes19961-0ubuntu8
ProcCmdline: /usr/bin/mythcommflag -j 2486 -V 3
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? () from /usr/lib/libmythtv-0.21.so.0
 ?? () from /usr/lib/libmythtv-0.21.so.0
 mpeg2_slice () from /usr/lib/libmythtv-0.21.so.0
 mpeg2_parse () from /usr/lib/libmythtv-0.21.so.0
 AvFormatDecoderPrivate::DecodeMPEG2Video ()
Title: mythcommflag crashed with SIGSEGV in mpeg2_slice()
Uname: Linux 2.6.28-14-generic x86_64
UserGroups: audio cdrom dialout video

Revision history for this message
Jaakan Shorter (jaakanshorter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:MC_put_o_16_mmxext (dest=0x7ffd45b4deb0 "",
motion_fr_frame_420 (decoder=0x7ffd44037c80,
mpeg2_slice (decoder=0x7ffd44037c80,
mpeg2_parse (mpeg2dec=0x7ffd44037c80)
AvFormatDecoderPrivate::DecodeMPEG2Video (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in mythtv (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu by reporting this issue. I am closing this ticket for a combination of reasons:

1. It is missing symbol information needed to help debug the issue (not your fault)
2. The decoders have been refreshed in the upcoming version (0.22)
3. There are no other reports of this issue
4. Mythtv developers upstream have stopped focusing on 0.21 based reports
5. This issue would need to be reproduced on 0.22 with a new stack trace

If you can reproduce this on 0.22, please attach traces to a new ticket and we can try to forward this bug upstream to get the right eyes focused on it.

We have builds of mythtv 0.22 available on a PPA to test. Please follow the directions at http://mythbuntu.org/auto-builds to enable them.

WARNING: If you intend to revert back to 0.21 after testing, you will need to back up your database before upgrading.

    Thanks again!

Changed in mythtv (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.