Project

General

Profile

Bug #5976

Deadlocks using HDHomerun

Added by Oliver Roe almost 4 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Crashes
Target version:
-
Start date:
2020-11-30
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1914~g214a14f29
Affected Versions:

Description

I've not been able to narrow down what causes it but i keep getting deadlocks which cause TVH to restart. I've supplied the deadlock log but please let me know which other logs i should be providing.

Thanks

Files

mutex-deadlock.txt (419 Bytes) mutex-deadlock.txt Oliver Roe, 2020-11-30 13:44
mutex-deadlock.txt (818 Bytes) mutex-deadlock.txt Deadlock 2 Oliver Roe, 2020-12-02 14:41
Log.txt.txt (390 KB) Log.txt.txt Oliver Roe, 2020-12-02 14:41

History

#1

Updated by Oliver Roe almost 4 years ago

The second deadlock file was created at 2020-12-02 13:30:55 which caused TVHeadend to restart (line 3359 of the log). I can't see anything in the log that help with the issue though

#2

Updated by Oliver Roe almost 4 years ago

Just to add, after the restart all HDHomerun tuner's are shown as being locked even though none are being used so I have to power down the tuners to use them

#3

Updated by Flole Systems almost 4 years ago

You need to check using gdb to see where the threads are at the moment, then you can find the cause. Probably there are 2 threads for waiting for each other, if you are able to figure out which ones there might be an easy fix.

#4

Updated by Oliver Roe almost 4 years ago

Thanks for the reply

I'm running TVH through Docker on a Synology NAS and I think gdb is a bit beyond me. It's ok to close the ticket

Also available in: Atom PDF