mythcommflag crashed with SIGSEGV in avcodec_decode_video2()

[Luke Morrison]

Unfortunately, this is all I know. I'm not a developer.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-backend 2:0.25.0+fixes.20120517.ec51a97-0ubuntu0mythbuntu4 [origin: LP-PPA-mythbuntu-0.25]
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythfilldatabase.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CrashCounter: 1
CrashDB: mythbuntu
Date: Fri May 18 01:32:17 2012
ExecutablePath: /usr/bin/mythcommflag
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythcommflag -j 235 --noprogress --verbose general --loglevel info --syslog local7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 ?? () from /usr/lib/libmythavcodec.so.52
 ?? () from /usr/lib/libmythavcodec.so.52
 ?? () from /usr/lib/libmythavcodec.so.52
 avcodec_decode_video2 () from /usr/lib/libmythavcodec.so.52
 ?? () from /usr/lib/libmythtv-0.25.so.0
Title: mythcommflag crashed with SIGSEGV in avcodec_decode_video2()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio cdrom dialout video

[Paul Wright (lytteltonwrights)]

About half of all the recordings that are scanned fail. This makes the system unstable and dies every 2-3 days. When commflag is turned off in setup then the system can be stable for a week (if something else doesn't crash).

[axel (simon-simonfoley)]

yup mythtv is a complete disaster area at the moment 2.5 2.6 loads of ringbuffer issues as well, so many issues its hard to work out the root cause of issues. Ill stop looking at ringbuffer issues in live tv today and see if i can find out what is going on here as its beginning to nag me.

[Luke Morrison (lukemorro)]

I have two HVR-950Qs attached to a splitter going to an indoor OTA antenna. Attempts to record more than one show at a time unless they are on the same multiplex have been fruitless, and I'm unable to watch LiveTV as it records on another, unless they are again on the same multiplex. For me, I believe it may be a signal strength issue, but I have not made the time to test this theory.

Luke

[paul summers (paulsum)]

mythcommflag fails on corrupt data from recorded tv shows... (using HDhomerun) ... on abc (which happens to be a weak station approx 80 miles away) has sometimes bad data... but the canadian station (city-tv) is local and also broadcasts the show.. modern family. but isnt weak thus it doesn't fail...
when i checked the mythbackend status... the job queue, the abc recording errored , but the same show recorded on city-tv at the same time... didn't error because it did not have errors in signal transmission. (for example signal drop outs etc)

the point is the i believe that the codec that decodes the channel breaks/crashes/has-issues with corrupted signals... the abc signal is 720p... whereas the city-tv channel is 1080i... but that is not the point. it is the mpeg2 stream that is "corrupted" breaks the mythcommflag searching... so the fix would be to skip the bad data fields.

not sure if this is the problem, but the mythcommflag "exit on error 140" correlates with a bad signal recording of HDTV recording.

[paul summers (paulsum)]

happened again... see my comment 5.

[paul summers (paulsum)]

yet again... crashes

[paul summers (paulsum)]

i have no problem watching tv... with a 2 hdhomerun boxes, recording 4 shows at once OTA, no problem. livetv, no problem...

but mythcommflagis a slight problem... works least 80 percent of the time (enough of a reason to stick with mythtv)...

(not a bug but annoying) when i turn off run mythcommflag (in mythbackend settup) the mythcommflag jobs pile up... so disabling it is not a solution.)

[paul summers (paulsum)]

know that this would happen again, so I installed a completely new install of mythbuntu (32 bit) , updated to all the usual updates, and installed 0.26 (repository method)... and lo and behold BUG... perhaps it is the amd and nvidia combo LOL... won't be able to test it on an intel processor until i can get one....

in any case it is a strange bug, because mythcommflag is still running, i.e this crash did not disrupt the commercial detection... so i guess that means it "relaunched" where it left off...

being a new install, i have recorded 14 shows, (so 14 mythcommflag queued jobs, but only 12 listed metadata lookups, so maybe it is the metadata lookup that is the problem no?)

but out of the 14 mythcommflag jobs, only 2 failed with exit status 140. (as listed in the job queue)

[Lee McLaren (lmclaren)]

Bog standard, new build, new hardware and it happens to me. I am using Avermedia PCIX tuners.

[George Bingham (georgeb1962)]

Happens whenever the signal is not strong.

[George Bingham (georgeb1962)]

Am using Hauppage 2250, digital tuner. This problem happens whenever the signal is not strong.

[paul summers (paulsum)]

not sure how this happened, but i did try mythcommflag on another file and it worked until it got to the end of the file, while mythcommflag did not "crash" it did not complete even though it made it to 99% complete (i know because i was checking the completion using mythweb) . run ended with a "exit eroor code 140

so a feature request would be to save the found commerical breaks as they are found instead of when it has completed scanning the show.

perhaps it did not like the end of the file (it was in 1080I, the rest of the shows are in 720p, and they have the commerical breaks marked)

TL;DR... this is an elusive bug... it does not crash on every show...

[paul summers (paulsum)]

happened once... shows got recorded and scanned... mythcommmflag for some reason crashes once only..

[paul summers (paulsum)]

it's back.... but this time mythcommflag errored out on "Rudolph the Red-Noseed Reindeer" cbc this day... (720p) i recorded it in progress (started at 8pm set a timer at 8:01 via guide.

recording it again on the 20 th so I'll see if that recording mythcommflag has "issues" seaching for commericals...

[paul summers (paulsum)]

mythcommflag exception in middle of checking "the simpsons" while recording...(but it is still recording)

[paul summers (paulsum)]

happy new year....(2013)

[j spam (knowtrash2009)]

mythcommflag exception is back to haunt me,
The problem is from cinnimon mate installation of the mythtv

[j spam (knowtrash2009)]

so mythcommflag keeps crashing. and crashing. this is a problem beyond me.

[j spam (knowtrash2009)]

i have not figured it out yet, has anybody else? any clues?

[j spam (knowtrash2009)]

A much of updates and the problem is still here.

[j spam (knowtrash2009)]

Doing more updates that showed up, hope they fix this MythcommFlag error.

[j spam (knowtrash2009)]

this error likes me. Even if i don't like it.

[j spam (knowtrash2009)]

some times it works and some times it does. How does one go about solving this problem?

[j spam (knowtrash2009)]

wow it happened again!

[j spam (knowtrash2009)]

okay it is the time to be jolley, even if MythcommFlag crashes, Merry Christmas to all and to all a Good Night!

[j spam (knowtrash2009)]

Yep, still a problem for me.

[j spam (knowtrash2009)]

by know there has to be enough info for some clue as to what is going on.

[j spam (knowtrash2009)]

SIGSEGV? most interesting!

[Thomas Mashos (tgm4883)]

I'm going to push this upsteam, but they will want new logs from a 0.27+fixes install.

1. Enable the mythbuntu update repo for 0.27
2. Update to the latest version of MythTV
3. Install the mythtv-dbg package
4. Wait for a crash to happen
5. File a bug report when the crash detector pops up. If it doesn't pop up, run 'ubuntu-bug mythtv-backend'. It will probably make a new bug report, so throw a link here in a comment to it.

[j spam (knowtrash2009)]

i did the following:
sudo apt-add-repository ppa:mythbuntu/0.27
 to add the Mythbuntu Updates repo, you would do "sudo apt-add-repository ppa:mythbuntu/testing"

update of mythtv to .27 from .25 was done
the mythtv-dbg package was included in the update that was done

Now waiting for crash to happen.

[j spam (knowtrash2009)]

Since i have upgraded to version 0.27, this error has not happened, but another error with URL opening has been happening.
Do I need to run step 5 from the above comment?

5. File a bug report when the crash detector pops up. If it doesn't pop up, run 'ubuntu-bug mythtv-backend'. It will probably make a new bug report, so throw a link here in a comment to it.

[Thomas Mashos (tgm4883)]

Yea. That is assuming that the part you are talking about is in mythtv
backend (which I think URL opening would be a funny thing to have in the
backend)
On Jun 22, 2014 8:55 PM, "j spam" <email address hidden> wrote:

> Since i have upgraded to version 0.27, this error has not happened, but
> another error with URL opening has been happening.
> Do I need to run step 5 from the above comment?
>
> 5. File a bug report when the crash detector pops up. If it doesn't pop
> up, run 'ubuntu-bug mythtv-backend'. It will probably make a new bug
> report, so throw a link here in a comment to it.
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
> https://bugs.launchpad.net/bugs/1001204
>
> Title:
> mythcommflag crashed with SIGSEGV in avcodec_decode_video2()
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> New
>
> Bug description:
> Unfortunately, this is all I know. I'm not a developer.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: mythtv-backend
> 2:0.25.0+fixes.20120517.ec51a97-0ubuntu0mythbuntu4 [origin:
> LP-PPA-mythbuntu-0.25]
> ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
> Uname: Linux 3.2.0-24-generic-pae i686
> .var.log.mythtv.mythavtest.log:
>
> .var.log.mythtv.mythccextractor.log:
>
> .var.log.mythtv.mythfilldatabase.log:
>
> .var.log.mythtv.mythjobqueue.log:
>
> .var.log.mythtv.mythlcdserver.log:
>
> .var.log.mythtv.mythmediaserver.log:
>
> .var.log.mythtv.mythshutdown.log:
>
> .var.log.mythtv.mythtranscode.log:
>
> .var.log.mythtv.mythutil.log:
>
> .var.log.mythtv.mythwelcome.log:
>
> ApportVersion: 2.0.1-0ubuntu7
> Architecture: i386
> CrashCounter: 1
> CrashDB: mythbuntu
> Date: Fri May 18 01:32:17 2012
> ExecutablePath: /usr/bin/mythcommflag
> Installed_mythtv_dbg: 0.0
> ProcCmdline: /usr/bin/mythcommflag -j 235 --noprogress --verbose general
> --loglevel info --syslog local7
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> Signal: 11
> SourcePackage: mythtv
> StacktraceTop:
> ?? () from /usr/lib/libmythavcodec.so.52
> ?? () from /usr/lib/libmythavcodec.so.52
> ?? () from /usr/lib/libmythavcodec.so.52
> avcodec_decode_video2 () from /usr/lib/libmythavcodec.so.52
> ?? () from /usr/lib/libmythtv-0.25.so.0
> Title: mythcommflag crashed with SIGSEGV in avcodec_decode_video2()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: audio cdrom dialout video
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1001204/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help : https://help.launchpad.net/ListHelp
>

[j spam (knowtrash2009)]

Now is the error from the backend or frontend of MythTV? I don't know.
i do know that it is from "mythtv" and it has been reported before.
I am not able to report the error this time, more updates are needed.
I must not be on a stable release, but when ever any thing is changed, i get the notice.

hope this helps someone.

/usr/share/mythtv/metadata/Movie/tmdb3.py
mythtv-common 2:0.27.1+fixes.20140618.aa822f5-0ubuntu0mythbuntu1
tmdb3.py crashed with URLError in do_open(): <urlopen error [Errno -2] Name or service not known>

[Thomas Mashos (tgm4883)]

That is in mythtv-common.
Thanks,

Thomas Mashos

On Fri, Jun 27, 2014 at 4:03 PM, j spam <email address hidden> wrote:
> Now is the error from the backend or frontend of MythTV? I don't know.
> i do know that it is from "mythtv" and it has been reported before.
> I am not able to report the error this time, more updates are needed.
> I must not be on a stable release, but when ever any thing is changed, i get the notice.
>
> hope this helps someone.
>
> /usr/share/mythtv/metadata/Movie/tmdb3.py
> mythtv-common 2:0.27.1+fixes.20140618.aa822f5-0ubuntu0mythbuntu1
> tmdb3.py crashed with URLError in do_open(): <urlopen error [Errno -2] Name or service not known>
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
> https://bugs.launchpad.net/bugs/1001204
>
> Title:
> mythcommflag crashed with SIGSEGV in avcodec_decode_video2()
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> New
>
> Bug description:
> Unfortunately, this is all I know. I'm not a developer.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: mythtv-backend 2:0.25.0+fixes.20120517.ec51a97-0ubuntu0mythbuntu4 [origin: LP-PPA-mythbuntu-0.25]
> ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
> Uname: Linux 3.2.0-24-generic-pae i686
> .var.log.mythtv.mythavtest.log:
>
> .var.log.mythtv.mythccextractor.log:
>
> .var.log.mythtv.mythfilldatabase.log:
>
> .var.log.mythtv.mythjobqueue.log:
>
> .var.log.mythtv.mythlcdserver.log:
>
> .var.log.mythtv.mythmediaserver.log:
>
> .var.log.mythtv.mythshutdown.log:
>
> .var.log.mythtv.mythtranscode.log:
>
> .var.log.mythtv.mythutil.log:
>
> .var.log.mythtv.mythwelcome.log:
>
> ApportVersion: 2.0.1-0ubuntu7
> Architecture: i386
> CrashCounter: 1
> CrashDB: mythbuntu
> Date: Fri May 18 01:32:17 2012
> ExecutablePath: /usr/bin/mythcommflag
> Installed_mythtv_dbg: 0.0
> ProcCmdline: /usr/bin/mythcommflag -j 235 --noprogress --verbose general --loglevel info --syslog local7
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> Signal: 11
> SourcePackage: mythtv
> StacktraceTop:
> ?? () from /usr/lib/libmythavcodec.so.52
> ?? () from /usr/lib/libmythavcodec.so.52
> ?? () from /usr/lib/libmythavcodec.so.52
> avcodec_decode_video2 () from /usr/lib/libmythavcodec.so.52
> ?? () from /usr/lib/libmythtv-0.25.so.0
> Title: mythcommflag crashed with SIGSEGV in avcodec_decode_video2()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: audio cdrom dialout video
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1001204/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help : https://help.launchpad.net/ListHelp

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.