[mythtv] [mythtv-commits] Ticket #5268: mythtv-backend seems to go into endless loop, pegs cpu

[Daniel Kristjansson]

On Tue, 2009-07-28 at 22:07 -0400, Michael T. Dean wrote:
> On 07/28/2009 09:24 PM, MythTV wrote:
> > #5268: mythtv-backend seems to go into endless loop, pegs cpu
> >
> > Comment(by eharris):
> >
> >  In case it is helpful, I've narrowed down what seems to be the cause of
> >  the problem.  Whenever the backend actually deletes a recording due to the
> >  backend getting below the minimum free space limit, shortly thereafter the
> >  system goes into the highly loaded continuous issuance of SCHEDULE_CHANGE
> >  messages.  Just to be clear, this is NOT caused when a program is marked

E. Harris, you probably need to debug a bit further, after you've made
sure you are running the latest fixes or trunk revision. The problem in
#5268 has been fixed. The general problem is an event socket being made
from the master backend to itself and hence causing events to be resent
endlessly, but AFAIK both reported instances of that type of bug that
have existed in the past have been fixed in both the current release
0.21 and trunk. I also don't know of any new code that could have
introduced this type of bug, hence the suspicion you may be running an
old revision, but this could of course be a new bug in which case we
really want to know about it.

PS The particular way you triggered the continuous issuance of the
event is probably not important, except perhaps as a good way to
make it repeatable. A SCHEDULE_CHANGE should be sent once the file
is deleted because we may now want to record another episode of the
series if it is a series and there is an episode limit.

-- Daniel