Project

General

Profile

Bug #5648

too much queued table input data (over 2MB)…, discarding new (related to EIT grabbing)

Added by Michał Sawicz about 2 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
Start date:
2019-06-08
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1792~g466a01431
Affected Versions:

Description

Hi,

I've just set up a TVHeadend server with TBS Octa 6909X on Ubuntu using the linuxserver.io docker image (version 4.3-1792~g466a01431, so current master).

The adapters seem to be working fine, however TVHeadend is quite unstable, I'm getting a lot of:

tvheadend    | 2019-06-08 02:46:24.078 [WARNING] mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6909x (Octa DVB-S/S2/S2X) #6 : DVB-S #0, discarding new
tvheadend    | 2019-06-08 02:46:29.250 [WARNING] mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6909x (Octa DVB-S/S2/S2X) #3 : DVB-S #0, discarding new
tvheadend    | 2019-06-08 02:46:29.946 [WARNING] mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6909x (Octa DVB-S/S2/S2X) #7 : DVB-S #0, discarding new
tvheadend    | 2019-06-08 02:46:34.459 [WARNING] mpegts: too much queued table input data (over 2MB) for TurboSight TBS 6909x (Octa DVB-S/S2/S2X) #6 : DVB-S #0, discarding new

When this happens, TVHeadend becomes unresponsive. It doesn't happen when only one subscription is active, but the more subscriptions (even EPG ones) activate, the more common the message above and TVHeadend becomes unusable.

As far I can tell, this is related to EPG grabbing. I was able to record 10 channels (as can be seen at the top of the log) in a stable manner. As soon as I stopped recording (that's when the attached trace starts) and epgrab kicked in, the problem came back.

I've seen this issue, but it's marked fixed some 10 commits before master.

Attached is a file with the traces enabled as asked in the above issue.

I'll be trying to bisect tvhdeadend to pinpoint the commit introducing this.


Files

tvheadend.log (393 KB) tvheadend.log Michał Sawicz, 2019-06-08 12:32

History

#1

Updated by Chris G almost 2 years ago

Same issue. I also use a TBS card 6908.

#2

Updated by saen acro almost 2 years ago

Do you see something similar on dmesg

[1319338.288218] tvh:mi-main[27299]: segfault at 178 ip 00007ff2ab6f1fa0 sp 00007ff2854e93f8 error 4 in libpthread-2.27.so[7ff2ab6e8000+1a000]
[1319538.333664] traps: tvh:mi-main[1267] general protection ip:7f5c031e9fa0 sp:7f5bddfee3f8 error:0 in libpthread-2.27.so[7f5c031e0000+1a000]

#3

Updated by Victor S about 1 year ago

Same issue TBS 6909x, TBS 6909, TVH 4.2, 4.3. Especially when UHD channels are tuned and trying to scan via another tuner, TVH slows down until these messages and eventually becomes unresponsive.

No there is nothing like that in DMESG.

Also available in: Atom PDF