[mythtv-commits] Ticket #7699: "locked" frontend and overloaded backend due to live TV Browse mode

[MythTV]

#7699: "locked" frontend and overloaded backend due to live TV Browse mode
------------------------------------------------+---------------------------
 Reporter:  Petr Stehlik <pstehlik@…>           |       Owner:  ijr    
     Type:  defect                              |      Status:  new    
 Priority:  minor                               |   Milestone:  unknown
Component:  MythTV - General                    |     Version:  unknown
 Severity:  medium                              |     Mlocked:  0      
------------------------------------------------+---------------------------
 0.22-fixes. Two DVB-S cards, two sources, almost the same channels on
 them. Identical channels set with the same channum and callsign so MythTV
 is free to pick up either of those tuners for a given channum or a
 callsign.

 In setup the following switches are enabled:
 - Avoid conflicts between live TV and scheduled shows
 - Allow live TV to move scheduled shows
 - Always use Browse mode in live TV
 - Browse all channels

 Multirecording enabled (with 5 simultaneous recordings).

 A scheduled recording in progress on card#1, live TV on card#2. Pressing
 ArrowUp/Down in live TV should show the Browse OSD and allow browsing
 through the channels. Instead the frontend stops responding to any key and
 backend maxes out the CPU (together with mysqld).

 frontend -v playback,channel repeats forever:
 00:07:58.936 IsTunable(9003)
 00:07:59.498 IsTunable(9003) -> false

 00:07:59.507 IsTunable(9003)
 00:07:59.836 IsTunable(9003) -> false

 00:07:59.845 IsTunable(9003)
 00:08:00.120 IsTunable(9003) -> false

 9003 is the first channel (channum "1"). I was recording channel "3" and
 watching live channel "5" so after pressing ArrowUp it should have checked
 IsTunable for channel "6" but there is another bug that causes the Browse
 mode to think the current channum is 0. There is a snippet of a log with
 Browse mode disabled:

 ChannelBase(10): Looking for startchannel 'NextChannel 0' on input
 'DVBInput #1'

 It shows that Myth is confused and tries to find next channel to channel
 "0" while I was watching channel "5" or something. I don't have channum
 "0" defined at all.

 Much more details can be found in this thread: http://www.gossamer-
 threads.com/lists/mythtv/users/410801

 Maybe it would be smarter to create a separate ticket just for the problem
 with zero current channel and when that would be fixed this "locked
 frontend" problem might be fixed as well, dunno.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7699>
MythTV <http://www.mythtv.org/>
MythTV