I think my mods went in on the 16th at about 11:58pm if I got my timezone
conversion correct in my head. If your runaway thread is indeed
niced and is using 99% cpu then you can try reproducing the problem
by compiling in debug mode as indicated in the docs and then run
mythcommflag inside gdb on the show last show you recorded. If you
killed the process there should be one show without commercials
flagged.
To see if ther are any un-flagged recordings, you can run mythcommflag
in test mode (see --help for options) or just do the following sql
query:
select chanid, starttime, type, count(*) from recordedmarkup
group by chanid, starttime, type order by starttime, chanid, type;
That should list a bunch of type 3, 4, and 5 records for each
recording. If there aren't any 4 or 5 records for a particular
chanid and starttime then that show wasn't flagged. You can
flag that show by running mythcommflag with the --chanid and
--starttime options. If you run it inside gdb and it hangs
then use CTRL-C to stop it and then do a backtrace as documented in
the Myth docs. When running mythcommflag from the command-line,
it WILL use all available cpu and WILL NOT nice itself. To get it
to not consume all available cpu, run with the --sleep option.
Run "mythcommflag --help" for more options.
> Sounds like what could be causing the problem, Im running from cvs I
> downloaded the 17th around 10 pm.
>
> --Jeff
>
> On Mon, 19 May 2003, Chris Pinkham wrote:
>
> > The commercial detection thread also performs a sleep after processing
> > each frame, so if you see a niced mythbackend and it's using 100% cpu
> > it must be stuck in a loop somewhere. I fixed a couple places where
> > this could happen just a few days ago.
> >
> > Are you running current CVS or is it a few days old?
> >
> > > On Monday 19 May 2003 11:33 am, jeff@burstable.net wrote:
> > > > ANyone else noticing high cpu utilizations from mythbackend from recent
> > > > cvs? I usually update to the latest CVS version every few days or so, so
> > > > I dont know when this started, but it seems that mythbackend is using 99%
> > > > cpu even when its just sitting there not recording. ANy idea what I
> > > > should be looking for to fix this?
> > >
> > > Most likely the commercial detection thread -- turn it off if you don't want
> > > it using CPU, but it's niced down to low priority so it shouldn't be hurting
> > > anything.
> >
> > Chris
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users@snowman.net
> > http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
> >
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>
--
Chris