Opened 14 years ago
Closed 14 years ago
#8978 closed defect (Fixed)
Deadlock in backend on starting a new recording
Reported by: | danielk | Owned by: | jpoet |
---|---|---|---|
Priority: | blocker | Milestone: | 0.24 |
Component: | MythTV - General | Version: | Master Head |
Severity: | high | Keywords: | |
Cc: | Ticket locked: | no |
Description
I'm setting this as a blocker for now. If it turns out to be rare I will reduce the priority. But I want to investigate this to at least determine if it is a recent regression.
Attachments (1)
Change History (4)
Changed 14 years ago by
Attachment: | 8978-dbg.txt added |
---|
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Owner: | changed from danielk to jpoet |
---|---|
Severity: | medium → high |
Status: | new → assigned |
It looks like m_SMpending is set and StartRecording?() will consequently block forever waiting for the signal quality to improve. This needs to be fixed, we can't have a poor signal on one recorder prevent all other recorders and the fronteds from working.. When StartRecording?() blocks it prevents the scheduler from running and prevents all backend calls that require a scheduler lock from completing...
Note: See
TracTickets for help on using
tickets.
Very little of value is in the backend log: