[mythtv-users] ringbuf in memory?

[Michael T. Dean]

On 12/19/2008 12:12 AM, Scott Harris wrote:
> Michael T. Dean wrote:
>   
>> On 12/18/2008 08:54 PM, Scott Harris wrote:
>>     
>>> but it still 
>>> suffers from
>>> random 3-10 second hangs in between key presses (not consistent, and irw
>>> shows the keys received)
>> That sounds like an issue ( 
>> http://www.gossamer-threads.com/lists/mythtv/commits/356391#356391 ) 
>> that was fixed in 0.21-fixes in r19222 (2 weeks ago).  If you're running 
>> an earlier version of -fixes, you may want to see if there's an upgrade 
>> available.
>>   
>>     
> Thanks, I'll check to see if there is a later release available.  I'm 
> using atrpms and am running
>
> mythtv-frontend-0.21-198.fc10.x86_64
> mythtv-backend-0.21-198.fc10.x86_64
> libmythtv-0.21_0-0.21-198.fc10.x86_64
> mythtv-0.21-198.fc10.x86_64
>
> This is the main system in the house so running a development version it 
> can be difficult to
> keep the WAF high if there are a lot of segfaults.

Yeah, it was fixed in 0.21-fixes, so no need to go to trunk.  The Fedora 
packages are all built with 0.21-fixes, so once they have a build of 
r19222 or later, you'll have the fix.

You can check your revision with "mythfrontend --version" or 
"mythbackend --version".  You'll get something like:

$ mythbackend --version
Please include all output in bug reports.
MythTV Version   : 19356
MythTV Branch    : branches/release-0-21-fixes
Library API      : 0.21.20080304-1
Network Protocol : 40
Options compiled in:
 linux release using_oss using_alsa using_jack using_backend using_dbox2 
using_dvb using_firewire using_frontend using_hdhomerun using_iptv 
using_ivtv using_joystick_menu using_lirc using_opengl_vsync 
using_opengl_video using_v4l using_x11 using_xrandr using_xv using_xvmc 
using_xvmc_opengl using_bindings_perl using_bindings_python using_opengl 
using_ffmpeg_threads using_libavc_5_3 using_live using_xvmc_pbuffer

Which says 0.21-fixes r19356.  If yours already says 19222 or later, 
you've got the fix, so it's something else.  If not, the bug is likely 
causing delays/non-responsiveness (as F10 is known to be affected by the 
bug).

Mike