[mythtv-commits] Ticket #7078: socket errors cause back-end to become unresponsive (trunk 21894)

[MythTV]

#7078: socket errors cause back-end to become unresponsive (trunk 21894)
------------------------------+---------------------------------------------
 Reporter:  databubble        |        Owner:  danielk   
     Type:  defect            |       Status:  infoneeded
 Priority:  major             |    Milestone:  0.22      
Component:  MythTV - General  |      Version:  head      
 Severity:  medium            |   Resolution:            
  Mlocked:  0                 |  
------------------------------+---------------------------------------------

Comment(by anonymous):

 Replying to [comment:3 anonymous]:
 > I have re-compiled with --compile-type=debug still with r21894 and the
 back-end is running now.  Some quick poking, and it hasn't triggered the
 problem yet.... and that log keeps getting bigger and bigger.  As soon as
 it does fall over (usually a few hours) I'll do my best to extract better
 quality information for you.

 I can confirm the same issue with:

 MythTV Version   : 21583-openglvdpau2-nv180
 MythTV Branch    : branches/release-0-21-fixes
 Network Protocol : 40
 Library API      : 0.21.20080304-1
 Options compiled in:
  linux profile using_oss using_alsa using_pulse using_jack using_backend
 using_directfb using_dvb using_firewire using_frontend
 using_glx_proc_addr_arb using_hdhomerun using_iptv using_ivtv
 using_joystick_menu using_libfftw3 using_lirc using_opengl_video
 using_opengl_vsync using_v4l using_x11 using_xrandr using_xv using_xvmc
 using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python
 using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live

 I have yet to find a way to trigger it, seems random but destroy WAF.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/7078#comment:4>
MythTV <http://www.mythtv.org/>
MythTV