[mythtv-commits] Ticket #12314: mythbackend deadlocked during record, EIT scan and reschedule. CPU goes to 100%.

[MythTV]

#12314: mythbackend deadlocked during record, EIT scan and reschedule. CPU goes to
100%.
----------------------------------------+------------------------
 Reporter:  Paul Netherwood <paul@…>    |          Owner:
     Type:  Bug Report - Hang/Deadlock  |         Status:  new
 Priority:  major                       |      Milestone:  0.27.5
Component:  MythTV - General            |        Version:  0.27.4
 Severity:  medium                      |     Resolution:
 Keywords:  deadlock 100% CPU           |  Ticket locked:  0
----------------------------------------+------------------------

Comment (by Paul Netherwood <paul@…>):

 I've just added two more stack traces, gdb.deadlocked.3.txt while
 mythbackend was locked and  gdb.deadlocked.3.after.txt immediately after
 after it unlocked itself about 5 minutes later. You can see in the
 deadlocked file that there are 7 threads all waiting on the same QMutex.
 They have gone in the second file. It looks like thet are all waiting on a
 lock in the same place. I suspect there is some locking issue in the
 scheduler. Note that these stacktraces are with the EIT scanner turned off
 and during one recording.

--
Ticket URL: <https://code.mythtv.org/trac/ticket/12314#comment:1>
MythTV <http://www.mythtv.org>
MythTV Media Center