[mythtv-commits] Ticket #7105: Broadcast H264 tuning fails due to cascade of thousands of log messages

[MythTV]

#7105: Broadcast H264 tuning fails due to cascade of thousands of log messages
-----------------------------------------------------+----------------------
 Reporter:  Matthew Grant <matthewgrant5 at gmail.com>  |       Owner:  ijr    
     Type:  defect                                   |      Status:  new    
 Priority:  critical                                 |   Milestone:  unknown
Component:  MythTV - General                         |     Version:  head   
 Severity:  high                                     |     Mlocked:  0      
-----------------------------------------------------+----------------------
 Race condition during tuning with broadcast H264 here in New Zealand.  Box
 was under heavy recording load, 5 shows being recorded to disk and Live TV
 browsing, lots of channel changing and it is painfully slow at doing it.
 Thousands of Log messages produced about:

 2009-09-20 07:35:21.687 [h264 @ 0x7f658b991a20]number of reference frames
 exceeds max (probably corrupt input), discarding one

 and 2nd choke point hidden by above:

 2009-09-20 10:43:57.123 DTVRec(35) Error: FindH264Keyframes: No ringbuffer

 mythbackend would then segfault away into oblivion.

 Fix/hack commenting out messages attached to ticket

 Box has 4 HD DB-T tuners Hauppauge HVR2200s, and 2 DVBS tuners, HVR4000,
 and an AMD PhenomII X4 CPU, NVida 9400GT video, (will use built in ATI
 HD3300 when drivers are good).

 With logging set to General,Important, while tuning mythbackend spends all
 its time formatting and logging error messages, which actually cascades
 and results in tuning failure - this would only show up in New Zealand or
 Norway as they are currently the only countries known to broadcast using
 the H264 codec.

 Work around is to set --verbose=none - this is how I determined it was the
 time spent formating thousands of log messages - not very useful if you
 want to know what else is going on...

 With this fix/hack in place TV watching works well here in NZ.

 Better solution would be to implement counters in static variables that
 tick over every few thousand and emit one log message...

 Comments about how to correct for merge would be appreciated.

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