Opened 11 years ago

Closed 11 years ago

#6905 closed defect (duplicate)

mythbackend hangs while recording

Reported by: David Asher <asherml@…> Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: MythTV - General Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no


I'm running trunk r21261 -- originally mytbuntu weekly build, but I rebuilt to get symbols.

I've had several situations where some portion of mythbackend becomes non-responsive while doing several back-to-back recordings w/real-time mythcommflag-ging. Then any job which needs to talk to the backend hangs. Sometimes it means I've got a generate-preview waiting, other times its a bunch of mythtv-status jobs, and mythweb always times out with some HTTP request error (sorry, I don't have the exact error -- i'll grab it next time). I've got a gdb.txt backtrace for the most recent one, this case was one with many hanging mythtv-status jobs. Please let me know anything I can do to help debug.

Oh, If I start mythbackend "--verbose all" it doesn't happen.

$ /usr/bin/mythbackend --version Please include all output in bug reports. MythTV Version : exported MythTV Branch : trunk Network Protocol : 46 Library API : 0.22.20090813-1 QT Version : 4.5.0 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_hdpvr using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit 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 using_mheg

Attachments (2)

gdb.txt.hang.24aug2145 (75.9 KB) - added by David Asher <asherml@…> 11 years ago.
backtrace for non-responsive mythbackend
mythbackend.log.hang (18.0 KB) - added by David Asher <asherml@…> 11 years ago.
mythbackend.log from the time where we become non-responsive

Download all attachments as: .zip

Change History (4)

Changed 11 years ago by David Asher <asherml@…>

Attachment: gdb.txt.hang.24aug2145 added

backtrace for non-responsive mythbackend

Changed 11 years ago by David Asher <asherml@…>

Attachment: mythbackend.log.hang added

mythbackend.log from the time where we become non-responsive

comment:1 Changed 11 years ago by David Asher <asherml@…>

I upgraded to r21507 and this hasn't happened since.

My guess is one of the (many) MythSocket? changes fixed things. Feel free to close and I'll reopen with a new backtrace if it happens again.

comment:2 Changed 11 years ago by danielk

Resolution: duplicate
Status: newclosed

dup #6516.

FYI It's not completely fixed yet, but it should now recover within a couple minutes. I'll ref #6516 when I commit the last of the mythsocket fixes.

Note: See TracTickets for help on using tickets.