Opened 13 years ago
Closed 12 years ago
#9261 closed Bug Report - Hang/Deadlock (Need more Info)
[HANG] Mythbackend hangs after upgrade to 0.24-fixes when try to start recording
Reported by: | Owned by: | stuartm | |
---|---|---|---|
Priority: | critical | Milestone: | 0.26 |
Component: | MythTV - EIT | Version: | 0.24-fixes |
Severity: | low | Keywords: | |
Cc: | Ticket locked: | no |
Description
After the upgrade to 0.24 when tring to start a recording, mythbackend stops responding. Backtrace and log is attached.
Attachments (2)
Change History (13)
comment:1 Changed 13 years ago by
Status: | new → assigned |
---|
comment:2 Changed 13 years ago by
Component: | MythTV - Recording → MythTV - EIT |
---|---|
Owner: | danielk deleted |
Priority: | major → minor |
Severity: | medium → low |
Status: | assigned → new |
comment:3 Changed 13 years ago by
Milestone: | → unknown |
---|---|
Owner: | set to Stuart Auchterlonie |
Status: | new → assigned |
comment:4 Changed 13 years ago by
I have same problem with my system and I can see same deadlock with EITScanner::lock on my gdb backtrace. Is it possible that EITScanner::RunEventLoop?() manages to monopolise lock so that EITScanner::StopPassiveScan? can't get lock? This link http://stackoverflow.com/questions/2121200/qmutex-stuck-in-locked-state suggests that it is possible scenario. Most of the RunEventLoop?() runs with lock activated most it's time especially when activeScan==false. One fact that speaks also for this is that I can do controlled shutdown for backend in couple seconds so it's deadlock that can be resolved. Could solution be that RunEventLoop?() is chanced so that it does sched_yield (or sleeps) when activeScan==false?
comment:5 Changed 13 years ago by
Summary: | Mythbackend hangs after upgrade to 0.24-fixes when try to start recording → [HANG] Mythbackend hangs after upgrade to 0.24-fixes when try to start recording |
---|
comment:7 Changed 12 years ago by
Milestone: | unknown → 0.25 |
---|---|
Owner: | changed from Stuart Auchterlonie to stuartm |
Priority: | minor → critical |
Status: | assigned → accepted |
Type: | Bug Report → Bug Report - Hang/Deadlock |
I'll take this, although I might be asking for input from Stuart A or Daniel
comment:8 Changed 12 years ago by
Status: | accepted → infoneeded |
---|
Is this repeatable with 0.25-rc? If not, let's close this as it is a report against a fairly old version of 0.24, and we have made a year's worth of changes since.
comment:9 Changed 12 years ago by
Milestone: | 0.25 → 0.25.1 |
---|
comment:10 Changed 12 years ago by
Milestone: | 0.25.1 → 0.26 |
---|
comment:11 Changed 12 years ago by
Resolution: | → Need more Info |
---|---|
Status: | infoneeded → closed |
This appears to be caused by a dead lock in the EIT shutdown code.