[mythtv-users] .25 two out of six shows tonight, no commercials flagged
david.madsen at gmail.com
Fri Apr 27 05:21:30 UTC 2012
On Thu, Apr 26, 2012 at 9:41 PM, Kenneth Emerson
<kenneth.emerson at gmail.com>wrote:
> On Thu, Apr 26, 2012 at 1:58 AM, Ian Evans <dheianevans at gmail.com> wrote:
>> Just noticed that I had a couple of shows not commercial flag tonight.
>> I would wager that your commflag process is segfaulting. What do you
> have on your status page / Job Queue in MythWeb? Does it show that the
> commflag jobs failed? If it doesn't show up at all, then there is
> something wrong processing your job queue.
> Since I've been running from master (for several months) my commflagging
> has been hit and miss. Around 25% of my commflag jobs segfault. Sometimes
> the segfault is in the ffmpeg code and the devs have said that is out of
> their hands (usually the statement is that the recording is corrupt). Other
> times it seems to be within the MythTV code. I have logged a ticket on one
> of these providing a backtrace.
> I also agree that back in the days of .24 mythcommflag never segfaulted.
> Over the past 3 days I've had 6 of 22 recordings fail on mythcommflag.
I've also seen a rather large increase in the number of segfaults from
mythcommflag after upgrading to 0.25. I haven't had time to do any further
debug yet, but all of my segfaults are happening in the libavcodec code
mythcommflag: segfault at ad0df000 ip b65d23bf sp ac7846ec error 4
mythcommflag: segfault at ad0df000 ip b66253bf sp ac28491c error 4
mythcommflag: segfault at acdd1000 ip b66323bf sp ac28491c error 4
mythcommflag: segfault at af3da01d ip b65a2b7f sp ac78491c error 4
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users