Modify
Warning Please read the Ticket HowTo before creating or commenting on a ticket. Failure to do so may cause your ticket to be rejected or result in a slower response.

Opened 21 months ago

Closed 21 months ago

Last modified 19 months ago

#10948 closed Bug Report - General (fixed)

EITScanner::StopActiveScan() && TVRec::SetChannel() deadlock

Reported by: stuartm Owned by: danielk
Priority: blocker Milestone: 0.26
Component: MythTV - Recording Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Backtrace attached

Attachments (1)

gdb.txt (123.4 KB) - added by stuartm 21 months ago.
Backtrace

Download all attachments as: .zip

Change History (5)

Changed 21 months ago by stuartm

Backtrace

comment:1 Changed 21 months ago by Daniel Thor Kristjansson <danielk@…>

  • Resolution set to fixed
  • Status changed from new to closed

In e8073bc0e9cbd3aaaaff85d6ca4ef12c79bf71d2/mythtv:

Fixes #10948. Fixes EIT shutdown deadlock.

comment:2 Changed 21 months ago by danielk

  • Summary changed from backend deadlock in TVRec::RecordPending() to EITScanner::StopActiveScan() && TVRec::SetChannel() deadlock

comment:3 Changed 21 months ago by Daniel Thor Kristjansson <danielk@…>

In 0e5d159c6bc98ef29a7b6bb225b43492b45c37ac/mythtv:

Refs #10948. Fully randomize EIT crawl start time.

The deadlocks we've been seeing here should be fixed now, but they
should have been rare to begin with due to randomization of the
EIT Scanning start time. But they were occurring at fairly high
frequency. It turns out we were not applying enough randomness when
there were multiple cards and we were also losing randomness after
the first recording on a tuner finished and we reset the clock.

comment:4 Changed 19 months ago by Daniel Thor Kristjansson <danielk@…>

In 957c7e20c8b9e2f2bb50a5fc826810c39689db4b/mythtv:

Refs #10948. Fully randomize EIT crawl start time.

The deadlocks we've been seeing here should be fixed now, but they
should have been rare to begin with due to randomization of the
EIT Scanning start time. But they were occurring at fairly high
frequency. It turns out we were not applying enough randomness when
there were multiple cards and we were also losing randomness after
the first recording on a tuner finished and we reset the clock.
(cherry picked from commit 0e5d159c6bc98ef29a7b6bb225b43492b45c37ac)

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'new'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.