<div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 26, 2012 at 9:41 PM, Kenneth Emerson <span dir="ltr"><<a href="mailto:kenneth.emerson@gmail.com" target="_blank">kenneth.emerson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div class="im">On Thu, Apr 26, 2012 at 1:58 AM, Ian Evans <span dir="ltr"><<a href="mailto:dheianevans@gmail.com" target="_blank">dheianevans@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just noticed that I had a couple of shows not commercial flag tonight.<br><br></blockquote></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>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.</div></div></div></blockquote><div><br>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 thus far.<br>
<br>mythcommflag[14031]: segfault at ad0df000 ip b65d23bf sp ac7846ec error 4 in libmythavcodec.so.52.113.1[b6174000+59a000]<br>mythcommflag[15577]: segfault at ad0df000 ip b66253bf sp ac28491c error 4 in libmythavcodec.so.52.113.1[b61c7000+59a000]<br>
mythcommflag[29788]: segfault at acdd1000 ip b66323bf sp ac28491c error 4 in libmythavcodec.so.52.113.1[b61d4000+59a000]<br>mythcommflag[31725]: segfault at af3da01d ip b65a2b7f sp ac78491c error 4 in libmythavcodec.so.52.113.1[b6144000+59a000]<br>
<br>--Dave<br></div></div></div>