Opened 12 years ago
Closed 2 years ago
#11127 closed Bug Report - Hang/Deadlock (Trac EOL)
deadlock in backend after recording device failure
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | needs_triage |
| Component: | MythTV - General | Version: | 0.25-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
I have been noticing a pattern here. My backend deadlocks and needs to be restarted after a recording failure presumably due to a device failure. This really should not happen.
Yes, I understand that trying to deal with hardware failure is not always easy, but hardware does fail, sadly. Having the backend become moribund when this happens is tragic, to put it nicely. Hardware failure should result in at most, a failed recording at the time. The backend should simply pick itself up and get on with life instead of lying down like a dead dog.
I will attach a backend log as well as a stack trace of this situation.
P.S. I am really trying to resist the urge to set the Priority and/or Severity on this ticket. This issue is very severe and should have the utmost priority, IMHO. WAF is nosediving fast and hard due to an entire night of favourite show season premiers for a whole night not recording due to a dual (multirec at the same time) recording failure.
Attachments (3)
Change History (6)
Changed 12 years ago by
| Attachment: | ThreadStacktrace.txt added |
|---|
comment:1 Changed 12 years ago by
I should add, that there were a number of deadlocks in that file, hence the several restarts over the last 12 hours or so. I will also attach the stack trace from this reboot that was needed this morning.
comment:2 Changed 4 years ago by
| Milestone: | unknown → needs_triage |
|---|
This definitely still happens, as i've experienced it recently
stack trace of deadlocked threads