Opened 9 years ago

Closed 9 years ago

#9473 closed Bug Report (Invalid)

Backend intermittently locks up

Reported by: mythtv@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Unspecified
Severity: medium Keywords:
Cc: Ticket locked: no

Description

On occasion - possibly only when watching live tv - my backend gets into a state where it will no longer respond to certain actions. The live tv playback ends, throwing the frontend back to the menu. It will not restart, and nor can I list my recordings. Also mythweb becomes unresponsive to requests for backend status, recorded programs, and upcomming recordings. Recording of programs seem to continue. Restarting mythbackend returns the system to a working state (although that of course stops any current recordings).

I didn't see this prior to upgrading to 0.24. Around the same time I added a Nova-S2 tuner to my system. After this happened a few times, I build a debug version, and then the problem seemed to stop, but I had another case of it last night. I've now obtained backtraces for all the running threads, hoping that might shed light on the problem.

I am using fixes/0.24 2394a9d70fe with a few local changes to H264Parser.cpp that cure problems with BBC HD programs.

Attachments (2)

stacks.txt (13.8 KB) - added by mythtv@… 9 years ago.
Backtraces
mythbackend.log (46.4 KB) - added by mythtv@… 9 years ago.
The backend log

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by mythtv@…

Attachment: stacks.txt added

Backtraces

Changed 9 years ago by mythtv@…

Attachment: mythbackend.log added

The backend log

comment:1 Changed 9 years ago by mythtv@…

Sorry, I tracked down my latest stall to a problem with my then H264Parser changes. During recording constant changes in aspect ratio were being misreported leading to the table recordedmarkup becoming huge. Attempts to sort that table stalled mysql, which in turn stalled mythbackend.

I don't believe the stalls I had in the past could be related to the latest one, but the past ones were some considerable time ago. I'd recommend closing this ticket. I can always rereport the problem it it recurs.

comment:2 Changed 9 years ago by robertm

Resolution: Invalid
Status: newclosed

Thank you for reporting back.

Note: See TracTickets for help on using tickets.