mythfrontend.real crashed with SIGABRT in av_image_copy_plane()

Bug #1406959 reported by Glenn Brumfield
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mythbuntu
New
Undecided
Unassigned

Bug Description

After reporting bug #1406956, I restarted mythfrontend, attempted to Watch TV (failed), checked MythWeather (successful), then attempted to check System Status. That is when the frontend crashed.

I don't know if this is related to the above listed bug. The only change I've made is to enable MythArchive just before I started getting these crashes.

Mythbuntu 14.04 version 0.27 with all updates.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: mythtv-frontend 2:0.27.4+fixes.20141212.40506c2-0ubuntu0mythbuntu2 [origin: LP-PPA-mythbuntu-0.27]
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CrashCounter: 1
CrashDB: mythbuntu
CurrentDesktop: XFCE
Date: Thu Jan 1 10:41:38 2015
ExecutablePath: /usr/bin/mythfrontend.real
InstallationDate: Installed on 2014-12-26 (5 days ago)
InstallationMedia: Mythbuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Installed_mythtv_dbg: 2:0.27.4+fixes.20141212.40506c2-0ubuntu0mythbuntu2
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mythtv
StacktraceTop:
 av_image_copy_plane (dst=0x8 <error: Cannot access memory at address 0x8>, dst_linesize=21440, src=0x7f4c04871000 '\200' <repeats 200 times>..., src_linesize=-1, bytewidth=1767990784, height=1) at libavutil/imgutils.c:248
 av_image_copy (dst_data=0x7f4aa80335d8, dst_linesizes=0x7f4aa8033618, src_data=src_data@entry=0x7f4aa8032940, src_linesizes=src_linesizes@entry=0x7f4aa8032980, pix_fmt=AV_PIX_FMT_YUVJ420P, width=32, height=976) at libavutil/imgutils.c:289
 decode_slice_header (h=h@entry=0x6bb41e0, h0=h0@entry=0x6bb41e0) at libavcodec/h264.c:3455
 decode_nal_units (parse_extradata=0, buf_size=22056, buf=0x7f4aa82dfa20 "", h=0x6bb41e0) at libavcodec/h264.c:4649
 decode_frame (avctx=0x6b6fd80, data=0x7f4abba0d720, got_frame=0x7f4abba0d658, avpkt=<optimized out>) at libavcodec/h264.c:4827
Title: mythfrontend.real crashed with SIGABRT in av_image_copy_plane()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo video

Revision history for this message
Glenn Brumfield (brumfield-glenn) wrote :
Revision history for this message
Glenn Brumfield (brumfield-glenn) wrote :

Happened again after watching a recording, erasing 3 recordings, and starting an audio stream.

Error message stated that Mythbackend Setup crashed, although Mythbackend Setup should not have been open.

Revision history for this message
Glenn Brumfield (brumfield-glenn) wrote :

Strike 3! I'll be ignoring further crashes of this program version.

information type: Private → Public
Revision history for this message
John Gelm (jgelm) wrote :

Continuation of Bug #1527313

So far, the messagebox has not popped up again.

I have been clicking on 'report problem' almost daily since Dec 4th. Today is the firt day I was asked to login to ubuntuone!

I thought error reports were being silently sent. Apparently not!

Revision history for this message
John Gelm (jgelm) wrote :

I linked the second occurrance of the messagebox as referenced in Bug #1527313 to this bug report because the title matched excatly. In effect, I have had two bug titles generated by your tracking system today.

Your tracking system has not included the attachments generated by THAT second messagebox.

Therefore, any attachments that were prepared by your tracking system were not passed on to you by your tracking system.

Unless advised otherwise, I will create a NEW bug each time I get the messagebox so you will get all the info generated by your system.

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.