Opened 8 years ago

Closed 8 years ago

#10423 closed Bug Report - General (fixed)

Setup UI locks up while scanning for channels

Reported by: helinf1@… Owned by: danielk
Priority: minor Milestone: 0.25
Component: MythTV - Mythtv-setup Version: Master Head
Severity: medium Keywords: channel scan
Cc: Ticket locked: no

Description

While testing 0.25-beta (v0.25-beta-58-g48ba349) I notice that mythtv-setup becomes unresponsive after scan of certain multiplexes. Manual scanning of individual multiplexes works for most multiplexes. A complete scan may run for a while and then seemingly stop at certain multiplexes. At this point the various options to cancel/abort/complete etc are still selectable in the UI, but the UI becomes unresponsive once any of these options is invoked.

The attached log is output through gdb with chanscan logging. At the end of the log there's a stack-trace of all active threads following an abort at the point where the UI becomes unresponsive.

Attachments (1)

scanlog (108.2 KB) - added by helinf1@… 8 years ago.
Log and stacktrace

Download all attachments as: .zip

Change History (7)

Changed 8 years ago by helinf1@…

Attachment: scanlog added

Log and stacktrace

comment:1 Changed 8 years ago by buehlmann@…

Reverting https://github.com/MythTV/mythtv/commit/146ee76929fe1b00fe218e9d3364fe22e0f14340 did solve it for me.

Please note that I am also using this patch for channel scanning: http://code.mythtv.org/trac/ticket/7486

comment:2 in reply to:  1 Changed 8 years ago by helinf1@…

Replying to buehlmann@…:

Please note that I am also using this patch for channel scanning: http://code.mythtv.org/trac/ticket/7486

These tickets do seem to be related. The scanner stops after reporting that it has found a number of "potential channels" on a multiplex without offering any further action to add or edit channel-records. Missing NIT seems to cause the scan to terminate prematurely, while the main thread keeps waiting for resources to be released.

comment:3 Changed 8 years ago by danielk

Status: newinfoneeded_new

Does it lockup when you don't use any patches?

comment:4 in reply to:  3 Changed 8 years ago by helinf1@…

Replying to danielk:

Does it lockup when you don't use any patches?

Yes. I haven't actually tried the patch from ticket 7486, but judging by the source it is when the analysis of the information obtained from a multiplex is missing information that the UI becomes unresponsive. The patch fills in the missing information. However, the scan and analysis of a multiplex should release all locks and resources on exit even if data seem incomplete.

comment:5 Changed 8 years ago by skerit@…

I had the same problems while scanning the Astra 1 satellite. Reverting the commit buehlmann mentioned fixed it for me.

comment:6 Changed 8 years ago by Github

Resolution: fixed
Status: infoneeded_newclosed

Fixes #10423. Refs #8744. Fixes A->B,B->A locking issue introduced in [146ee7692]

Branch: master Changeset: f30ffd4b4a9ce16d6c7bcb604e09e07a9e61f3a3

Note: See TracTickets for help on using tickets.