[mythtv-commits] Ticket #7528: Backend Deadlock during rescheduling
MythTV
mythtv at cvs.mythtv.org
Tue Nov 10 14:37:23 UTC 2009
#7528: Backend Deadlock during rescheduling
-----------------------------------------------+----------------------------
Reporter: Jelle Foks <jelle-mythtv@…> | Owner: gigem
Type: defect | Status: assigned
Priority: minor | Milestone: unknown
Component: MythTV - Scheduling | Version: unknown
Severity: medium | Mlocked: 0
-----------------------------------------------+----------------------------
Comment(by Jelle Foks <jelle-mythtv@…>):
Thanks, the patch looks fine to me, I'll try it soon.
Maybe it needs a certain setup or recordings-schedule to trigger...
Sometimes the bug would not trigger for weeks, then suddenly more than
once
in a week... I have multiple tuners and many recordings scheduled (e.g.
record as many new movies as possible at the lowest priority, ditto local
news broadcasts etc). My setup is almost never idle.
But what about the (other) call to UpdateMatches() in
FillRecordListFromDB()
(which can be called from mainserver.cpp), shouldn't that then be done
while
holding the recordmatchLock too? And how about AddNewRecords(), which has
a
"UPDATE recordmatch ", and is called from FillRecordList(), which is
called
twice in scheduler.cpp without holding that lock.
Also: AddNotListed() uses the table and is also called from
FillRecordList()
without holding the lock.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/7528#comment:4>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list