[mythtv] [mythtv-commits] Ticket #8367: Log storm from bad h264 decoded video

[Robin Gilks]

> On 04/19/2010 12:45 AM, MythTV wrote:
>> #8367: Log storm from bad h264 decoded video
>> -------------------------------------------+--------------------------------
>>   Reporter:  Robin Gilks<g8ecj@…>           |       Owner:  janne
>>       Type:  defect                         |      Status:  new
>>   Priority:  minor                          |   Milestone:  unknown
>> Component:  MythTV - Video Playback        |     Version:  0.23rc2
>>   Severity:  medium                         |     Mlocked:  0
>> -------------------------------------------+--------------------------------
>>   Unrelated to #7982, error messages swamp the nfs network connection
>> which
>>   cause error messages that swamp the nfs network connection which
>>   cause......
>>
>>   Averaging 8 messages per millisecond to the log. Currently running
>> with no
>>   '-v' options at all (i.e. mythfrontend>  /home/mythtv/mythfrontend.log
>>   2>&1)
>>
>>   2010-04-19 08:14:39.440 [h264 @ 0x7f301f5da500]number of reference
>> frames
>>   exceeds max (probably corrupt input), discarding one
>>
>
> Robin,
>
> Those messages are considered errors by libav*, so they're reported
> (since changes for #6729) at the general level of verbosity.  The MythTV
> default verbosity is -v important,general .  Because errors should be
> reported in default verbosity, libav* errors will likely remain at
> general verbose level.  So, if you don't want to see them, you'll need
> to run at -v important (or, whatever verbosity that doesn't include
> general).

Thanks Mike - only saw this message after I'd added a comment to #6729 so
that can be unlocked again :-)

In line with most logging systems (eg syslogd), duplicate messages should
be suppressed though, especially in the default (empty command line) case.

If ever I get back to doing C++ programming again, I'll send in a patch.
In the meantime I've got another kernel module to code...


-- 
Robin Gilks